[JIRA] (JENKINS-38538) Old runs disappearing from stage view?
Title: Message Title Cornelius Riemenschneider created an issue Jenkins / JENKINS-38538 Old runs disappearing from stage view? Issue Type: Bug Assignee: Sam Van Oort Components: pipeline-stage-view-plugin Created: 2016/Sep/27 1:12 PM Priority: Minor Reporter: Cornelius Riemenschneider Hi, this may not be a bug but a support issue... Is there anywhere documented how/when old runs are not displayed anymore? Sometimes, not even one former run is displayed, sometimes it's up to 9 or so. It would be very nice to be able to compare to previous runs... There are two things in our setup which could cause this: Our pipeline jobs are autogenerated via the Jobs DSL, and so regularly, so the jobs DSL usually runs in between builds. We skip certain stages dynamically: If the artifact has been built, the stage is never even entered. We do so to now skew the average execution time for a stage, but could this confuse the stage view plugin? Add Comment
[JIRA] (JENKINS-38536) Execution time of parallel blocks of in-flight jobs wrong
Title: Message Title Cornelius Riemenschneider created an issue Jenkins / JENKINS-38536 Execution time of parallel blocks of in-flight jobs wrong Issue Type: Bug Assignee: Sam Van Oort Components: pipeline-stage-view-plugin Created: 2016/Sep/27 1:00 PM Priority: Minor Reporter: Cornelius Riemenschneider Hi, the execution time of a stage containing two parallel jobs shows, after the first job has finished, only the execution time of the first job, as long as the second job is running. After the second job has finished, the displayed time is updated to the right runtime. It would be nice if the time could be right during the execution of the job as well. Add Comment
[JIRA] (JENKINS-38510) Add a count to the locks to allow limited ressources
Title: Message Title Cornelius Riemenschneider created an issue Jenkins / JENKINS-38510 Add a count to the locks to allow limited ressources Issue Type: New Feature Assignee: Unassigned Components: lockable-resources-plugin Created: 2016/Sep/26 2:40 PM Priority: Major Reporter: Cornelius Riemenschneider Hi, somehow we need to throttle the concurrency of a build step. Using a lock doesn't quite fit the use case, as then we can't use concurrency at all, we'd prefer to say "This lock is available 3 times" and then have our build step concurrently execute up to 3 times, but not 5. Is this feasible to implement this in this plugin? Add Comment
[JIRA] [gitlab-plugin] (JENKINS-35218) Gitlab plugin with job dsl doesn't use gitlab CI features anymore
Title: Message Title
Cornelius Riemenschneider created an issue
Jenkins / JENKINS-35218
Gitlab plugin with job dsl doesn't use gitlab CI features anymore
Issue Type:
Bug
Assignee:
Robin Müller
Components:
gitlab-plugin, job-dsl-plugin
Created:
2016/May/30 10:53 AM
Environment:
Jenkins 2.6 Job DSL 1.47 Gitlab plugin 1.2.3
Priority:
Minor
Reporter:
Cornelius Riemenschneider
Hi,
the aforementioned versions of the Job DSL + the gitlab plugin don't activate the GitLabCommitStatusPublisher needed for the CI features of Gitlab to work. The line is missing from the generated xml, which is needed because we want to show gitlab that builds are in progress, to get the results of jenkins jobs to gitlab merge requests etc. Our job dsl snippet for the gitlab trigger is: triggers { gitlabPush { acceptMergeRequestOnSuccess(false) buildOnPushEvents(false) buildOnMergeRequestEvents(true) enableCiSkip(false) addNoteOnMergeRequest(true) addVoteOnMergeRequest(true) rebuildOpenMergeRequest("source") setBuildDescription(true) useCiFeatures(true) }
}
