Learn more about these different git repos.
Other Git URLs
I'm trying to build up the CI system for fedora-module-defaults. When handling pull-requests, I need to be able to identify the branch (or commit-ish) that the PR is targeted for merge against so that I can test whether changed files have bumped the version field in their contents (or otherwise there may be merge conflicts that will break DNF updates).
It does not appear that any data is passed to Jenkins that can be consumed by the .cico.pipeline and turned into environment variables to allow me to pass the baseline commit-ish to my test scripts.
As a short-term workaround, I have CI running only for PRs that are filed against the master branch (and hard-code the baseline), but I really need to be able to support PRs against other branches.
master
Can we please have a new variable that can be consumed by .cico.pipeline that provides the target branch?
Metadata Update from @pingou: - Issue tagged with: RFE
Metadata Update from @pingou: - Issue set to the milestone: 5.5
Metadata Update from @pingou: - Issue assigned to pingou
Commit fd1956e fixes this issue
Thanks! Is there an ETA on when this will land in production on pagure.io?
It's marked for pagure 5.5 https://pagure.io/pagure/roadmap/5.5/ which is due in April 7th.
Login to comment on this ticket.