opendevstack / opendevstack/ods-core

Error in Jenkins CI due to Atlassian Bitbucket license expired

Open
#1,175 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Shell
Stars
53
Forks
34
Avg merge
3h 26m
Merged PRs (30d)
1

Description

Describe the bug
Since ODS Box generation takes between 5 and 6 hours and atlassian license is only for 3 hours, we fail installation because atlassian Bitbucket license gets out of time.

To Reproduce
Steps to reproduce the behavior:
Run the Jenkins CI

Expected behavior
Should not fail.

Screenshots
If applicable, add screenshots to help explain your problem.

Affected version (please complete the following information):

  • OpenDevStack [e.g. 4.x]

Log Output (ensure to remove any confidential information like tokens, project names, etc.

21:15:55      amazon-ebs: Pushing quickstarter git repo to http://bitbucket.odsbox.lan:7990/scm/unitt/unitt-nginx-iq-test.git
21:15:55      amazon-ebs: [Pipeline] sh
21:15:55      amazon-ebs: WARNING: Unknown parameter(s) found for class type 'org.jenkinsci.plugins.workflow.steps.durable_task.ShellStep': label
21:15:55      amazon-ebs: ++ git rev-parse --abbrev-ref HEAD
21:15:55      amazon-ebs: + git push -u origin master
21:15:55      amazon-ebs: fatal: remote error: License limit exceeded
21:15:55      amazon-ebs: Your evaluation license is expired. Pushing has been disabled until the license
21:15:55      amazon-ebs: is brought back into compliance.
21:15:55      amazon-ebs:
21:15:55      amazon-ebs: Visit Bitbucket at http://bitbucket.odsbox.lan:7990 for more details.
21:15:55      amazon-ebs: [Pipeline] }
21:15:55      amazon-ebs: [Pipeline] // dir
21:15:55      amazon-ebs: [Pipeline] }
21:15:55      amazon-ebs: [Pipeline] // stage
21:15:55      amazon-ebs: [Pipeline] echo
21:15:55      amazon-ebs: [Push to remote-nginx-iq-test] **** ENDED stage 'Push to remote' for component 'nginx-iq-test' branch 'experimental' **** (took 1474 ms)
21:15:55      amazon-ebs: [Pipeline] }
21:15:55      amazon-ebs: [Pipeline] // node
21:15:55      amazon-ebs: [Pipeline] }
21:15:55      amazon-ebs: [Pipeline] // podTemplate
21:15:55      amazon-ebs: [Pipeline] End of Pipeline
21:15:55      amazon-ebs: ERROR: script returned exit code 128
21:15:55      amazon-ebs: Finished: FAILURE 

Additional context
Add any other context about the problem here.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running the Jenkins CI flow and tracing ODS Box generation through the Bitbucket push shown in the log. Inspect the Bitbucket license configuration and the long-running installation path; done means the 5–6 hour installation completes and the repository push succeeds without the license-limit error.

Written by the indexing model from the issue text.

Assessment

Domain
ci-cd, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.