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

Don't attempt deployment on ci.jenkins.io #130

Closed
NotMyFault opened this issue Oct 13, 2022 · 3 comments
Closed

Don't attempt deployment on ci.jenkins.io #130

NotMyFault opened this issue Oct 13, 2022 · 3 comments
Assignees

Comments

@NotMyFault
Copy link
Member

Every build fails at the moment, because executing the build logic provided by the makefile attempts to deploy the image to the docker hub: https://ci.jenkins.io/job/Infra/job/ircbot/job/main/14/

Maybe we can outsource the logic to the Jenkinsfile and use a isInfra() condition to check, whether the pipeline is executed on ci.j or infra.ci.j. Depending on the result, the pipeline deploys the image to the docker hub. There's no need to attempt that on ci.j, given we can't deploy from there.

For comparison, the build succeeds on infra.ci: https://infra.ci.jenkins.io/job/docker-jobs/job/ircbot/job/main/

@lemeurherve lemeurherve self-assigned this Oct 13, 2022
@lemeurherve
Copy link
Member

I've added the repository jenkins4eval/ircbot in the docker hub, and set its permissions for the "members" group, and restarted a build, it should fix it.

@lemeurherve
Copy link
Member

@lemeurherve
Copy link
Member

Finished: SUCCESS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants