[JIRA] (JENKINS-47891) Bitbucket branch source plugin does not understand the new Bitbucket Server webhooks
Title: Message Title Torsten Kleiber commented on JENKINS-47891 Re: Bitbucket branch source plugin does not understand the new Bitbucket Server webhooks Thank you, that was the missing piece, not it works! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47891) Bitbucket branch source plugin does not understand the new Bitbucket Server webhooks
Title: Message Title Torsten Kleiber commented on JENKINS-47891 Re: Bitbucket branch source plugin does not understand the new Bitbucket Server webhooks I'm on bitbucket-branch-source 2.4.1 and Bitbucket Server 5.16. Native Webhooks does not work for Pull requests here: Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47891) Bitbucket branch source plugin does not understand the new Bitbucket Server webhooks
Title: Message Title Torsten Kleiber updated an issue Jenkins / JENKINS-47891 Bitbucket branch source plugin does not understand the new Bitbucket Server webhooks Change By: Torsten Kleiber Attachment: native_webhooks.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50880) Create a new option for running when condition before stage input
Title: Message Title Torsten Kleiber commented on JENKINS-50880 Re: Create a new option for running when condition before stage input Thanks, works as requested. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54331) Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13
Title: Message Title Torsten Kleiber closed an issue as Fixed Jenkins / JENKINS-54331 Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13 Change By: Torsten Kleiber Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54331) Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13
Title: Message Title Torsten Kleiber updated JENKINS-54331 Jenkins / JENKINS-54331 Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13 Change By: Torsten Kleiber Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54331) Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13
Title: Message Title Torsten Kleiber commented on JENKINS-54331 Re: Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13 Not reproducible anymore with Bitbucket Branch Source Plugin 2.2.15 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54331) Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13
Title: Message Title Torsten Kleiber updated JENKINS-54331 Jenkins / JENKINS-54331 Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13 Change By: Torsten Kleiber Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49447) Using a milestone before an input will abort older build if there is a failure while the older build wait for a user input
Title: Message Title
Torsten Kleiber commented on JENKINS-49447
Re: Using a milestone before an input will abort older build if there is a failure while the older build wait for a user input
Here an example of a declarative Pipeline, where 2 input exists and therefore the workaround does not work:
pipeline {
agent any
stages {
stage ("Ask 1") {
steps {
input message: 'Ask 1'
milestone ordinal: 1
sh '''
echo $BUILD_NUMBER
if [ `echo "${BUILD_NUMBER} % 3" | bc` -eq 0 ]
then
exit 1
fi'''
}
}
stage ("Ask 2") {
steps {
input message: 'Ask 2'
milestone ordinal: 2
}
}
}
}
test case 1 - breaking job kills wainting jobs before:
start build 1, answer input "Ask 1" with proceed
start build 2, answer input "Ask 1" with proceed
start build 3, answer input "Ask 1" with proceed
> build with build number, which can divided by 3 breaks by default and cancels all waiting job before
test case 2 - cancel job kills wainting jobs before:
start build 1, answer input "Ask 1" with proceed
start build 2, answer input "Ask 1" with proceed, answer input "Ask 2" with cancel or cancel the build via the executor cancel button
> canceled build cancels all waiting job before
Add Comment
[JIRA] (JENKINS-54349) Logs are not correctly shown when parallel stage are skipped by when directive
Title: Message Title
Torsten Kleiber created an issue
Jenkins / JENKINS-54349
Logs are not correctly shown when parallel stage are skipped by when directive
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
parallel_stages.png
Components:
blueocean-plugin
Created:
2018-10-30 15:27
Environment:
Jenkins 2.138.2
Priority:
Major
Reporter:
Torsten Kleiber
pipeline {
agent any
options {
buildDiscarder logRotator(artifactNumToKeepStr: '5', numToKeepStr: '5')
}
stages {
stage ("Parallel") {
parallel {
stage ("Path 1") {
steps {
sh 'sleep 60'
}
}
stage ("Path 2") {
when {
branch 'dummy_for_easy_stage_skip'
beforeAgent true
}
steps {
sh 'sleep 60'
}
}
}
}
}
}
As long this pipeline runs you cannot see the log for the stage "Path 1". This is problematic on long runs with many steps. Additional the message "Queued: Waiting for run to start" on both stages is misleading, as the first stage is running and the second stage is skipped
[JIRA] (JENKINS-54331) Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13
Title: Message Title Torsten Kleiber created an issue Jenkins / JENKINS-54331 Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13 Issue Type: Bug Assignee: Unassigned Attachments: 1_new_plugin_version_two_jenkins_builds.png, 2_new_plugin_only_last_build_update_is_shown_1.png, 3_new_plugin_only_last_build_update_is_shown.png, 4_new_plugin_only_last_build_update_is_shown.png, 5_old_plugin_version_two_jenkins_builds.png, 6_old_plugin_2_builds_of_branch_and_pr_are_shown.png, 7_old_plugin_2_builds_of_branch_and_pr_are_shown.png Components: bitbucket-branch-source-plugin Created: 2018-10-30 07:27 Environment: Jenkins 2.138.2, Bitbucket Branch Source Plugin 2.2.13 Priority: Major Reporter: Torsten Kleiber We use here Bitbucket Merge Checks. We have defined 2 required successful build for merge, one for the branch itself and one for the pull request. This ensure that the master remains clean after the merge. Till 2.2.12 both builds are shown in Bitbucket. From 2.2.13 on only the last branch or pull request build update is shown, so the merge check can never fulfilled anymore!
[JIRA] (JENKINS-53734) Declarative pipeline - Support for parallel stages inside sequential stages
Title: Message Title Torsten Kleiber commented on JENKINS-53734 Re: Declarative pipeline - Support for parallel stages inside sequential stages I don't agree that this should not be rendered! Visualization of a pipeline for end user is important! Every other job control software has no problem with such parallelisation's. And for optimization of build time I need a lot of parallelisation's. So I would request the corresponding changes in blue ocean too after implementation of this change. In the meantime I run in several issues in Jenkins, where implementing one change in some plugin contradicts other restrictions in another plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50880) Create a new option for running when condition before stage input
Title: Message Title
Torsten Kleiber commented on JENKINS-50880
Re: Create a new option for running when condition before stage input
This workaround blocks an executor for the time waiting for input. Following is wanted (as described in https://jenkins.io/blog/2018/04/09/whats-in-declarative/)
pipeline {
agent none // no executor is blocked
stages {
stage('Production Deploy') {
when {
branch 'master'
// beforeInput: true
}
input {
message 'Deploy to Production?' // For this input can be waited several days
}
agent any // From here on for executing the steps an executor is needed
steps {
echo 'Deploying to Production ... '
}
}
}
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49447) Using a milestone before an input will abort older build if there is a failure while the older build wait for a user input
Title: Message Title Torsten Kleiber commented on JENKINS-49447 Re: Using a milestone before an input will abort older build if there is a failure while the older build wait for a user input Changed to critically as waiting jobs for deployment are cacelled and in combination with buildDiscarder are removed after this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49447) Using a milestone before an input will abort older build if there is a failure while the older build wait for a user input
Title: Message Title Torsten Kleiber edited a comment on JENKINS-49447 Re: Using a milestone before an input will abort older build if there is a failure while the older build wait for a user input Changed to critically as waiting jobs for deployment are cacelled cancelled and in combination with buildDiscarder are removed after this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49447) Using a milestone before an input will abort older build if there is a failure while the older build wait for a user input
Title: Message Title Torsten Kleiber updated an issue Jenkins / JENKINS-49447 Using a milestone before an input will abort older build if there is a failure while the older build wait for a user input Change By: Torsten Kleiber Priority: Minor Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53659) support for parallel Stages nested in stages for ressource locking
Title: Message Title
Torsten Kleiber created an issue
Jenkins / JENKINS-53659
support for parallel Stages nested in stages for ressource locking
Issue Type:
New Feature
Assignee:
Andrew Bayer
Components:
lockable-resources-plugin, pipeline-model-definition-plugin
Created:
2018-09-19 13:49
Environment:
Jenkins 2.138.1
Priority:
Critical
Reporter:
Torsten Kleiber
I don't want nest parallel in parallel. My use case is locking a resource for the parallel and sequential stages as a whole:
pipeline {
agent any
stages {
stage('Lock wrapper') {
options {
lock('resource')
}
stages {
stage('Sequential 1') {
steps {
echo "Sequential 1"
}
}
stage('Sequential 2') {
parallel {
stage('Parallel 2a') {
steps {
echo "Parallel 2a"
}
}
}
}
}
}
}
}
But this gives following error: Parallel stages or branches can only be included in a top-level stage. My final pipeline has far more than these stages, so lock of the whole pipeline is not an option.
[JIRA] (JENKINS-49447) Using a milestone before an input will abort older build if there is a failure while the older build wait for a user input
Title: Message Title Torsten Kleiber commented on JENKINS-49447 Re: Using a milestone before an input will abort older build if there is a failure while the older build wait for a user input Same happens, when user aborts the input or the whole build. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49447) Using a milestone before an input will abort older build if there is a failure while the older build wait for a user input
Title: Message Title Torsten Kleiber commented on JENKINS-49447 Re: Using a milestone before an input will abort older build if there is a failure while the older build wait for a user input The mentioned workaround unfortunatly means running in another bug: https://issues.jenkins-ci.org/browse/JENKINS-46097 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46097) Milestone can be passed by older build if another build exits early
Title: Message Title Torsten Kleiber commented on JENKINS-46097 Re: Milestone can be passed by older build if another build exits early The mentioned workaround unfortunatly means running in another bug: https://issues.jenkins-ci.org/browse/JENKINS-49447 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51174) no message is shown in stage view and log, when user is not authorized for input step
Title: Message Title
Torsten Kleiber created an issue
Jenkins / JENKINS-51174
no message is shown in stage view and log, when user is not authorized for input step
Issue Type:
New Feature
Assignee:
Unassigned
Attachments:
2018-05-07 11 19 42.png, 2018-05-07 11 20 13.png
Components:
pipeline-input-step-plugin
Created:
2018-05-07 09:30
Environment:
Jenkins ver. 2.107.2, SLES 11.4
Priority:
Major
Reporter:
Torsten Kleiber
Assuming following Pipeline:
pipeline {
agent none
stages {
stage ("Input") {
input {
message 'Are you sure?'
submitter 'not_me'
}
agent any
steps {
sh 'sleep 60'
}
}
}
}
if you press the butto to accept the input no message is shown in the stage view and in log view too It is only shown from the executor menu item pause/resume or blue ocean.
[JIRA] (JENKINS-51172) wrong pause image in the train after accepting an input step
Title: Message Title
Torsten Kleiber created an issue
Jenkins / JENKINS-51172
wrong pause image in the train after accepting an input step
Issue Type:
New Feature
Assignee:
Unassigned
Attachments:
2018-05-07 10 55 43.png
Components:
blueocean-plugin
Created:
2018-05-07 09:06
Environment:
Jenkins ver. 2.107.2, SLES 11.4
Priority:
Major
Reporter:
Torsten Kleiber
consider following pipeline:
pipeline {
agent none
stages {
stage ("Input") {
input {
message 'Are you sure?'
}
agent any
steps {
sh 'sleep 10'
}
}
}
}
If you accept the red marked input step icon does not change in blue ocean:
[JIRA] (JENKINS-50887) Need a buildDiscarder in a pipeline, which deletes only failing jobs in master branch
Title: Message Title Torsten Kleiber commented on JENKINS-50887 Re: Need a buildDiscarder in a pipeline, which deletes only failing jobs in master branch Have added branch as filter to this project. Build Status is already there. When are the projects selected which are implemented? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50887) Need a buildDiscarder in a pipeline, which deletes only failing jobs in master branch
Title: Message Title Torsten Kleiber updated an issue Jenkins / JENKINS-50887 Need a buildDiscarder in a pipeline, which deletes only failing jobs in master branch Change By: Torsten Kleiber For regulatory logging we have to keep all builds of a pipeline, which reaching production.These are the successfull successful ones .All other can be deleted after some time.This should be a new property of the buildDiscarderThese configuration should be depending on the branch, maybe this last part can be solved by a when expresssion but maybe a Multi branch configuration of buildDiscarder is required. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50887) Need a buildDiscarder in a pipeline, which deletes only failing jobs in master branch
Title: Message Title Torsten Kleiber created an issue Jenkins / JENKINS-50887 Need a buildDiscarder in a pipeline, which deletes only failing jobs in master branch Issue Type: New Feature Assignee: Unassigned Components: core Created: 2018-04-19 06:01 Environment: Jenkins ver. 2.107.2 Priority: Critical Reporter: Torsten Kleiber For regulatory logging we have to keep all builds of a pipeline, which reaching production. These are the successfull. All other can be deleted after some time. This should be a new property of the buildDiscarder These configuration should be depending on the branch, maybe this last part can be solved by a when expresssion but maybe a Multi branch configuration of buildDiscarder is required. Add Comment
[JIRA] (JENKINS-48379) Input/parameters for Stages
Title: Message Title Torsten Kleiber commented on JENKINS-48379 Re: Input/parameters for Stages Don't understand - what do you mean by this? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48379) Input/parameters for Stages
Title: Message Title Torsten Kleiber commented on JENKINS-48379 Re: Input/parameters for Stages Thanks I have bookmarked this, but not read before. Stage timeouts seems what I need! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48379) Input/parameters for Stages
Title: Message Title Torsten Kleiber edited a comment on JENKINS-48379 Re: Input/parameters for Stages But when I need a timeout around the input step, I must use this inside step and the executor is blocked again. So we need timeout too in stage. My requirement is, that when a deployment is not proceeded in a defined time, the the pipeline has to be cancelled. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48379) Input/parameters for Stages
Title: Message Title Torsten Kleiber commented on JENKINS-48379 Re: Input/parameters for Stages But when I need a timeout around the input step, the executor is blocked again. My requirement is, that when a deployment is not proceeded in a defined time, the the pipeline has to be cancelled. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50469) "No scm content provider found for pipeline" when using blue ocean pipeline editor in github organzation folder
Title: Message Title Torsten Kleiber edited a comment on JENKINS-50469 Re: "No scm content provider found for pipeline" when using blue ocean pipeline editor in github organzation folder Have not seen this hint before:*"Obsolete* plugin. May be removed after you have upgraded to 1.6."What does this mean? Do I have to add all of my repository manual now? Or do I find similar functionality somewhere else?Additional I don't see this in my installed plugins, so that I can deinstall this?Or is creating "GitHub Organization" not releated to this plugin? This was what I have done before! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50469) "No scm content provider found for pipeline" when using blue ocean pipeline editor in github organzation folder
Title: Message Title Torsten Kleiber edited a comment on JENKINS-50469 Re: "No scm content provider found for pipeline" when using blue ocean pipeline editor in github organzation folder Have not seen this hint before:*"Obsolete* plugin. May be removed after you have upgraded to 1.6."What does this mean? Do I have to add all of my repository manual now? Or do I find similar functionality somewhere else? Additional I don't see this in my installed plugins, so that I can deinstall this?Or is creating "GitHub Organization" not releated to this plugin? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50469) "No scm content provider found for pipeline" when using blue ocean pipeline editor in github organzation folder
Title: Message Title Torsten Kleiber commented on JENKINS-50469 Re: "No scm content provider found for pipeline" when using blue ocean pipeline editor in github organzation folder Have not seen this hint before: "Obsolete plugin. May be removed after you have upgraded to 1.6." What does this mean? Do I have to add all of my repository manual now? Or do I find similar functionality somewhere else? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50469) "No scm content provider found for pipeline" when using blue ocean pipeline editor in github organzation folder
Title: Message Title Torsten Kleiber created an issue Jenkins / JENKINS-50469 "No scm content provider found for pipeline" when using blue ocean pipeline editor in github organzation folder Issue Type: Bug Assignee: Unassigned Components: blueocean-pipeline-editor-plugin Created: 2018-03-28 21:08 Environment: Jenkins ver. 2.107.1 on Ubuntu 17.10.1 with Blue Ocean 4.1.2 Browser Chrome Version 65.0.3325.181 on Windows 10 Priority: Major Reporter: Torsten Kleiber I have a fresh creation of GitHub Organization Folder for my user tkleiber. Scan was succesfully. I then change to repository de.kleiber.cba and branch master. There I want to change the Jenkinsfile in the editor. When I try to edit and save the pipeline in the editor, then the error message "No scm content provider found for pipeline" is shown. Add Comment
[JIRA] (JENKINS-43267) JaCoCo plugin2.2.0 shows 100% coverage for 0 classes
Title: Message Title Torsten Kleiber updated an issue Jenkins / JENKINS-43267 JaCoCo plugin2.2.0 shows 100% coverage for 0 classes Change By: Torsten Kleiber Attachment: 2.2.0.png Attachment: 2.1.0.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43267) JaCoCo plugin2.2.0 shows 100% coverage for 0 classes
Title: Message Title Torsten Kleiber created an issue Jenkins / JENKINS-43267 JaCoCo plugin2.2.0 shows 100% coverage for 0 classes Issue Type: Bug Assignee: Ognjen Bubalo Components: jacoco-plugin Created: 2017/Mar/31 11:49 AM Environment: Jenkins ver. 2.46.1 on SLES 11.4 Priority: Blocker Reporter: Torsten Kleiber Rolling back to plugin 2.1.0 and rerunning my job shows again the real coverage and find all of my classes. Have not changed any plugin properties. Path to exec files: */*.exec Path to class directories: **/artefakte/build/lib/ikb (there are a lot of *.jars, no direct *.class files) Path to source directories: **/src Add Comment
[JIRA] (JENKINS-38811) Blue Ocean does not start on Internet Explorer 11
Title: Message Title Torsten Kleiber commented on JENKINS-38811 Re: Blue Ocean does not start on Internet Explorer 11 Yes beta 10 fix the error, thanks! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38811) Blue Ocean does not start on Internet Explorer 11
Title: Message Title Torsten Kleiber commented on JENKINS-38811 Re: Blue Ocean does not start on Internet Explorer 11 Maybe a virtual machine will help? Sure you have to install selenium after that, but this could be done via puppet or other: https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/ Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38811) Blue Ocean does not start on Internet Explorer 11
Title: Message Title Torsten Kleiber commented on JENKINS-38811 Re: Blue Ocean does not start on Internet Explorer 11 Same here. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38811) Blue Ocean does not start on Internet Explorer 11
Title: Message Title Torsten Kleiber updated an issue Jenkins / JENKINS-38811 Blue Ocean does not start on Internet Explorer 11 Change By: Torsten Kleiber Attachment: blueocean.js Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38811) Blue Ocean does not start on Internet Explorer 11
Title: Message Title Torsten Kleiber commented on JENKINS-38811 Re: Blue Ocean does not start on Internet Explorer 11 Have save the file blueocean.js from ie debugger. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38811) Blue Ocean does not start on Internet Explorer 11
Title: Message Title
Torsten Kleiber commented on JENKINS-38811
Re: Blue Ocean does not start on Internet Explorer 11
Error is reproducible furthermore, here is the copy of the ie console: HTML1300: Navigation wurde ausgeführt. Datei: blue TypeError: Die Eigenschaft "apply" eines undefinierten oder Nullverweises kann nicht abgerufen werden. { [functions]: , _proto_: { [functions]: , _proto_: { [functions]: , _proto_: { }, message: "", name: "Error" }, message: "", name: "TypeError" }, description: "Die Eigenschaft "apply" eines undefinierten oder Nullverweises kann nicht abgerufen werden.", message: "Die Eigenschaft "apply" eines undefinierten oder Nullverweises kann nicht abgerufen werden.", name: "TypeError", number: -2146823281, stack: "TypeError: Die Eigenschaft "apply" eines undefinierten oder Nullverweises kann nicht abgerufen werden. at startApp (/adjuncts/0d1e912c/io/jenkins/blueocean/blueocean.js:84892:9) at Anonymous function (/adjuncts/0d1e912c/io/jenkins/blueocean/blueocean.js:84932:5) at nextArg (/adjuncts/0d1e912c/io/jenkins/blueocean/blueocean.js:7006:25) at _filterExtensions (/adjuncts/0d1e912c/io/jenkins/blueocean/blueocean.js:7050:17) at Anonymous function (/adjuncts/0d1e912c/io/jenkins/blueocean/blueocean.js:7018:17) at checkLoading (/adjuncts/0d1e912c/io/jenkins/blueocean/blueocean.js:7146:21) at Anonymous function (/adjuncts/0d1e912c/io/jenkins/blueocean/blueocean.js:7174:17) at dec (/adjuncts/0d1e912c/io/jenkins/blueocean/blueocean.js:7212:17) at Anonymous function (" }
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google
[JIRA] (JENKINS-38811) Blue Ocean does not start on Internet Explorer 11
Title: Message Title Torsten Kleiber commented on JENKINS-38811 Re: Blue Ocean does not start on Internet Explorer 11 Please inform me, when this is available via a new beta, then I will retest this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38811) Blue Ocean does not start on Internet Explorer 11
Title: Message Title Torsten Kleiber commented on JENKINS-38811 Re: Blue Ocean does not start on Internet Explorer 11 See ie_console.png, unfortunately the messages are in german, Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38811) Blue Ocean does not start on Internet Explorer 11
Title: Message Title Torsten Kleiber updated an issue Jenkins / JENKINS-38811 Blue Ocean does not start on Internet Explorer 11 Change By: Torsten Kleiber Attachment: ie_console.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38811) Blue Ocean does not start on Internet Explorer 11
Title: Message Title Torsten Kleiber updated an issue Jenkins / JENKINS-38811 Blue Ocean does not start on Internet Explorer 11 Change By: Torsten Kleiber Attachment: 20161007_092922.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38811) Blue Ocean does not start on Internet Explorer 11
Title: Message Title Torsten Kleiber created an issue Jenkins / JENKINS-38811 Blue Ocean does not start on Internet Explorer 11 Issue Type: Bug Assignee: Unassigned Attachments: 20161007_092922.png Components: blueocean-plugin Created: 2016/Oct/07 7:31 AM Environment: Jenkins LTS 2.19.1 on SLES 11 SP 4 Internet Explorer 11.0.9600.18449 on Windows 7 Enterprise (Version 6.1 Build 7601 SP 1) BlueOcean beta 1.0.0-b07 Priority: Major Reporter: Torsten Kleiber Blue Ocean hangs on the last 5 percent of the blue loading bar before start on Internet Explorer. Works fine when running on chrome 51.0.2704.103 m on same computer. Add Comment
[JIRA] (JENKINS-37515) pipeline input blocks the executor
Title: Message Title Torsten Kleiber updated an issue Jenkins / JENKINS-37515 pipeline input blocks the executor Change By: Torsten Kleiber Attachment: build_history_with_more_builds_as_log_rotation.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37515) pipeline input blocks the executor
Title: Message Title Torsten Kleiber updated an issue Jenkins / JENKINS-37515 pipeline input blocks the executor Change By: Torsten Kleiber Attachment: log_rotation.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37515) pipeline input blocks the executor
Title: Message Title Torsten Kleiber commented on JENKINS-37515 Re: pipeline input blocks the executor This is a little bit confusing: the build history shows all the jobs running until you proceed or abort any job instande. Additional old "running" jobs are not deleted by log rotation. So how to batch delete old job instances or timeout these? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37515) pipeline input blocks the executor
Title: Message Title Torsten Kleiber reopened an issue See my last comment. Jenkins / JENKINS-37515 pipeline input blocks the executor Change By: Torsten Kleiber Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37515) pipeline input blocks the executor
Title: Message Title
Torsten Kleiber edited a comment on JENKINS-37515
Re: pipeline input blocks the executor
In which version do you have tested this, does not work in 2.7.2 here with following example !20160912_070739.png|thumbnail! : {{ node { stage 'Build after Commit'}stage 'Deploy against developement'input 'Are you sure?' }}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37515) pipeline input blocks the executor
Title: Message Title
Torsten Kleiber edited a comment on JENKINS-37515
Re: pipeline input blocks the executor
In which version do you have tested this, does not work in 2.7.2 here with following example !20160912_070739.png|thumbnail! :{ { node { stage 'Build after Commit'}stage 'Deploy against developement'input 'Are you sure?'} }
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37515) pipeline input blocks the executor
Title: Message Title
Torsten Kleiber commented on JENKINS-37515
Re: pipeline input blocks the executor
In which version do you have tested this, does not work in 2.7.2 here with following example : node { stage 'Build after Commit' } stage 'Deploy against developement' input 'Are you sure?'
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37515) pipeline input blocks the executor
Title: Message Title Torsten Kleiber updated an issue Jenkins / JENKINS-37515 pipeline input blocks the executor Change By: Torsten Kleiber Attachment: 20160912_070739.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19121) Build pipeline plugin no longer prompts for parameters of parameterised job
Title: Message Title Torsten Kleiber commented on JENKINS-19121 Re: Build pipeline plugin no longer prompts for parameters of parameterised job Unfortunatly not. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19121) Build pipeline plugin no longer prompts for parameters of parameterised job
Title: Message Title Torsten Kleiber commented on JENKINS-19121 Re: Build pipeline plugin no longer prompts for parameters of parameterised job That is the same reason why I don't have switched to pipeline (formerly workflow) plugin. Please vote for the corresponding Issue: https://issues.jenkins-ci.org/browse/JENKINS-37515 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37515) pipeline input blocks the executor
Title: Message Title Torsten Kleiber created an issue Jenkins / JENKINS-37515 pipeline input blocks the executor Issue Type: Bug Assignee: Oleg Nenashev Components: pipeline-_unsorted Created: 2016/Aug/18 1:12 PM Environment: Jenkins LTS 2.72 rpm on SLES 11 SP 4 Priority: Major Reporter: Torsten Kleiber When using an input step in pipeline, the executor is blocked until you proceed or abort the input step. We have here the case that the code is build whenever it is changed in the scm via polling. Only a small number of the builds going to development, staging and production. As the executor is blocked, the maximum number of executors is reached in short time. The build pipeline plugin instead use an executor for every job it contains. Is it possible to break end the executor when input step is reached and restart after proceed answer? Add Comment
