Currently Jenkins build jobs are executed using pki-jenkins-bot/pki repository: https://travis-ci.org/pki-jenkins-bot/pki/
The repository should be moved into dogtagpki organization (e.g. dogtagpki/pki-build). This will allow members of the organization to monitor or control (e.g. cancel, restart) the build jobs.
Metadata Update from @mharmsen: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None - Issue priority set to: critical - Issue set to the milestone: 1.0 TASKS
Metadata Update from @mharmsen: - Issue assigned to dmoluguw
There are a few information and things that needs to be done before the repository can be merged.
Note:
Developers won't be able to use this repository. This will be a dummy repository with 1 master branch that includes dummy README - to provide info about this repo. Like this: https://github.com/pki-jenkins-bot/pki/blob/master/README.md
The branches will be created temporarily and will be removed. So, basically this repository has no point moving to the official dogtagpki repo.
If moved, things to be done:
pki-jenkins-bot
Fixed in production.
Updated ansible scripts. Git commit: https://github.com/dogtagpki/pki-ci/commit/854cc11b45a93e57f35c40d1107a8371bf52cb9c
Repo being used: dogtagpki/pki-verification-ci Travis Repo: dogtagpki/pki-verification-ci
dogtagpki/pki-verification-ci
Metadata Update from @dmoluguw: - Issue close_status updated to: fixed
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/3052
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.