codex-storage / codex.storage

https://codex.storage
0 stars 3 forks source link

Jenkins jobs are not being triggered #35

Closed yakimant closed 11 months ago

yakimant commented 11 months ago

Both jobs are not being triggered:

Probably due to the move acid-info/codex.storage to codex-storage/codex.storage

I tried the following:

  1. Add status-im-auto as Admin to the repo
  2. Change configuration from acid-info/codex.storage to codex-storage/codex.storage
  3. "Re-register hooks for all jobs" in GitHub plugin advanced settings: https://ci.infra.status.im/manage/configure

It still shows acid in the logs:

GitHub webhooks activated for job website/codex.storage with [GitHubRepositoryName[host=github.com,username=acid-info,repository=codex.storage]] (events: [PUSH])
yakimant commented 11 months ago

After removing the webhook from GitHub and "" the following message is shown in Job configuration:

The webhook for repo acid-info/codex.storage on github.com failed to be registered or was removed. More info can be found on the global configuration page. This message will be dismissed if Jenkins receives a PING event from repo webhook or if you add the repo to the ignore list in the global configuration. Smth got wrong, will recreate dev job.

yakimant commented 11 months ago

Copied job has the following in the logs:

GitHub webhooks activated for job website/dev.codex.storage new with [] (events: [PUSH])
yakimant commented 11 months ago

Ok, the following helped:

  1. Remove GitHub webhook in the repo
  2. Created configurations from scratch (with new repo URL)
  3. Run job manually in each
  4. "Re-register hooks for all jobs"

Webhook was registered and now I see proper log line:

GitHub webhooks activated for job website/dev.codex.storage with [GitHubRepositoryName[host=github.com,username=codex-storage,repository=codex.storage]] (events: [PUSH])

Probably related issue: https://issues.jenkins.io/browse/JENKINS-37217

Looks like Jenkins doesn't really support repo move. You need to recreate a configuration from scratch.

yakimant commented 11 months ago

Fixed and tested. @jeangovil, feel free to reopen if you find any issues. @jakubgs, please review, when you are back

jakubgs commented 10 months ago

Yes, running Re-register hooks for all jobs often helps, but in some rare cases a job has to be recreated.