-
Notifications
You must be signed in to change notification settings - Fork 45
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
[BXMSPROD-2019] Productized branch creation #967
Conversation
String repoCredsId = repoConfig.author?.credentials_id ?: readMainBranchConfig().git.author.credentials_id | ||
|
||
// TODO is this value saved somewhere such that we do not have to hardcode? | ||
String jobsGroovyPath = '.ci/jenkins/dsl/jobs.groovy' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
where could we save this path in order to avoid hardcoding it? maybe we can simply save it on the branch.yaml, wdyt?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in the env ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I decided to put it in the branch.yaml > jenkins > jobs_definition_file
[1] to make it more customizable, wdyt?
// def jobsGroovy = readFile file: jobsGroovyPath | ||
// remove fullProfile | ||
sh "sed -i 's/, addFullProfileJobParamsGetter)/)/g' ${jobsGroovyPath}" | ||
// TODO: disable pr checks in getMultijobPRConfig, get them from params |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be the last remaining part to implement, disable PR checks from jobs.groovy
file.
I would do that in a separate PR as I need to re-think a bit what is the best way to handle it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need to redo the way the PR checks are generated in those repositories, to make it more dynamic, based on:
- build-chain-config
- or a file in
.ci
folder (name to be considered)
we can discuss about that if you want
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree as at the moment to disable them we should manipulate the file and it could be tricky to fully automate, furthermore changes on the file could also easily break the automation as it would be. So I agree on rethink how to setup those jobs.
|
looks like it was a temporary/random issue :/ it was using forked drools branch that was not existing anymore (maybe cached?) - now all green |
Linked https://github.com/kiegroup/optaplanner/pull/2845 to setup DSL changes on OptaPlanner repo too |
String repoCredsId = repoConfig.author?.credentials_id ?: readMainBranchConfig().git.author.credentials_id | ||
|
||
// TODO is this value saved somewhere such that we do not have to hardcode? | ||
String jobsGroovyPath = '.ci/jenkins/dsl/jobs.groovy' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in the env ?
// def jobsGroovy = readFile file: jobsGroovyPath | ||
// remove fullProfile | ||
sh "sed -i 's/, addFullProfileJobParamsGetter)/)/g' ${jobsGroovyPath}" | ||
// TODO: disable pr checks in getMultijobPRConfig, get them from params |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need to redo the way the PR checks are generated in those repositories, to make it more dynamic, based on:
- build-chain-config
- or a file in
.ci
folder (name to be considered)
we can discuss about that if you want
JIRA: https://issues.redhat.com/browse/BXMSPROD-2019
Referenced Pull Requests:
deploy artifacts configurable
Improvements: