Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ini setting ordering requirement is problematic #24

Open
bac opened this issue Dec 12, 2014 · 0 comments
Open

ini setting ordering requirement is problematic #24

bac opened this issue Dec 12, 2014 · 0 comments
Labels

Comments

@bac
Copy link

bac commented Dec 12, 2014

In the ini file there are two settings which have lists of Jenkins jobs and Github projects, namely jenkins.merge.job and github.project. It is unobvious but the jobs and projects listed here must match 1:1, that is if the nth item it github.project has a job to run, it will be assigned to the nth job in jenkins.merge.job.

It is not clear that the order matters and is easy to get wrong if many projects are listed.

It would be better to have an explicit mapping in the INI file, the equivalent of a list of tuples, however that might be realized in the config settings.

@bac bac added the bug label Dec 12, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant