[JIRA] (JENKINS-45925) Show git commit message when building with parameter "revision"
Title: Message Title Boguslaw Klimas started work on JENKINS-45925 Change By: Boguslaw Klimas Status: Open In Progress 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-52533) Display commit messsage on the build action
Title: Message Title Boguslaw Klimas started work on JENKINS-52533 Change By: Boguslaw Klimas Status: Open In Progress 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-38471) Git parameterized job always builds master
Title: Message Title Boguslaw Klimas closed an issue as Incomplete If it continues to exist on the current version of the plugin. Please attach some more information (project configuration, logs) and reopen this issue Jenkins / JENKINS-38471 Git parameterized job always builds master Change By: Boguslaw Klimas Status: Open Closed Resolution: Incomplete 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-28597) GIT Parameter Plugin not using stored credentials
Title: Message Title Boguslaw Klimas closed an issue as Not A Defect I close this issue because Plugin not store any credentials, plugin using the SCM define form project It's very old issue perhaps is no longer valid Jenkins / JENKINS-28597 GIT Parameter Plugin not using stored credentials Change By: Boguslaw Klimas Status: Open Closed Resolution: Not A Defect 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-42575) GIT Parameter latest version plugin is not showing the revision numbers in dropdown list
Title: Message Title Boguslaw Klimas closed an issue as Incomplete Jenkins / JENKINS-42575 GIT Parameter latest version plugin is not showing the revision numbers in dropdown list Change By: Boguslaw Klimas Status: Open Closed Resolution: Incomplete 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-53733) % Character in Password Created Error in User Creation
Title: Message Title Emmanuel Oginni created an issue Jenkins / JENKINS-53733 % Character in Password Created Error in User Creation Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-09-22 20:17 Environment: Jenkins ver. 2.138.1 Priority: Major Reporter: Emmanuel Oginni Use of % character in user password caused error in creating the user Add Comment
[JIRA] (JENKINS-26439) Build does not abort when «Send files or execute commands over SSH» fails
Title: Message Title Alex Earl commented on JENKINS-26439 Re: Build does not abort when «Send files or execute commands over SSH» fails This would be a change in behavior to the current plugin, I am not sure how many people are relying on the current behavior. I'll have to think about this some more. 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-51933) Publish Over CIFS action settings do not function when selected as a promotion action
Title: Message Title Alex Earl closed an issue as Fixed This should be in 0.11 Jenkins / JENKINS-51933 Publish Over CIFS action settings do not function when selected as a promotion action Change By: Alex Earl Status: Open Closed Resolution: Fixed Released As: 0.11 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-22217) Integrate with Jenkins Credentials Management
Title: Message Title Alex Earl commented on JENKINS-22217 Re: Integrate with Jenkins Credentials Management I am actively working on this...I just have to do it for all of the publish-over plugins at the same time since most of the logic is in a shared 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-26801) nested wariables not expanded
Title: Message Title Alex Earl closed an issue as Won't Fix Nested variables are outside the scope of this plugin Jenkins / JENKINS-26801 nested wariables not expanded Change By: Alex Earl Status: Open Closed Resolution: Won't Fix 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-41975) Multiple servers configuration ssh : jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config
Title: Message Title Alex Earl commented on JENKINS-41975 Re: Multiple servers configuration ssh : jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config I'm not sure I understand the issue, can you please describe what is going wrong? 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-37726) Publish Over SSH plugin: shebang is fully ignored
Title: Message Title Alex Earl closed an issue as Not A Defect The commands that you are executing are not run under the shell, it's like the commands are being executed as if you typed them one by one. If you want to do this, you would need to copy the shell script over to the server, then you could do /bin/bash yourfile.sh. This is different from the sh step for instance, where a shell script is created and then executed. Jenkins / JENKINS-37726 Publish Over SSH plugin: shebang is fully ignored Change By: Alex Earl Status: Open Closed Resolution: Not A Defect 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-44611) Any way to restrict build for non-whitelisted users?
Title: Message Title Jonathan Gray commented on JENKINS-44611 Re: Any way to restrict build for non-whitelisted users? 100% agree. The GHPRB plugin which appears to have now been deprecated in favor of github-branch-source-plugin has a major feature gap that appears to have been misunderstood here. This is a blocker issue for us on migrating away from GHPRB, and from a security perspective we're currently in a less than desirable position since GHPRB seems to presently have security issues. As a maintainer of an OSS project running a self-hosted Jenkins instance for the community, I want to build all PRs by those who are trusted contributors (which may be more than just those with merge rights) automatically. For those who are not trusted, the PR build needs to be authorized via PR comment by a trusted user before it is built. This should support Multibranch pipeline style jobs via Jenkinsfile so that the build process itself may be updated by untrusted OSS contributors. This approval pipeline/step/check is critical because you must protect against malicious PR modifications of a Jenkinsfile. 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-53635) xunit step failure is not displayed
Title: Message Title Nikolas Falco updated JENKINS-53635 Jenkins / JENKINS-53635 xunit step failure is not displayed Change By: Nikolas Falco Status: Reopened 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-34311) execute scripts on axes after all build steps are finished
Title: Message Title Daniel Heid updated an issue Jenkins / JENKINS-34311 execute scripts on axes after all build steps are finished Change By: Daniel Heid Environment: jenkins 1.647postbuildscript-plugin 0.17 Matrix Project Plugin 1.6 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-34311) execute scripts on axes after all build steps are finished
Title: Message Title Daniel Heid commented on JENKINS-34311 Re: execute scripts on axes after all build steps are finished Thanks for improving the PostBuildScript plugin, but I'm not sure, that I understood the feature request properly. Why not simply put a second build step after the first one? Could you please provide a config.xml so that it will be clearer for me? 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-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title
Andrew a commented on JENKINS-46507
Re: Parallel Pipeline random java.lang.InterruptedException
Hi everyone. A little info on this issue that we've been hitting as well. We're using jenkins and it's pipeline plugin to run our regression and ci builds for a SoC (System-on-chip) we're designing. As a side effect of what we're doing - some tests (under the parallel step) take a very long time to complete and are very CPU-intensive. Here's some statistics I've noticed:
CI builds that have a small amount (~10) of short tests under parallel step almost always complete successfully.
Regression runs that take a few days to complete and have a huge list of longer tests almost always hit this bug.
If the jenkins was restarted fresh, chances to hit this bug are somewhat lower. I came to think it was related to a memory leak in jenkins test-results-analyzer plugin at first, which (due to our huge, sometime over 500MiB log files) crashed jenkins often at fist, until I started filtering logs to mitigate the issue (https://issues.jenkins-ci.org/browse/JENKINS-34134). Tuning GC options seemed to further improve things.
Since we're running builds on NFS filesystem to later distribute and execute tests on different servers, thus balancing the load, I first considered filesystem lags due to other tasks being run on our servers. Adding this seemed to improve things a little bit. The disk load is not evenly distributed. It's heavy on the start of the test (when the model is loaded to memory and during reset due to extensive logging), later it's usually very low throughout the whole run.
/* Workaround laggy filesystem */
script {
System.setProperty("org.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL", "3800");
}
5. Another thing I've noticed, some tests seem to randomly fail. According to the simulation log, the simulation process was just killed (by something other than OOM), rather that getting stuck, and that happens quite fast (e.g. the simulation haven't even completed the reset sequence, which takes a few seconds of real time, but usually spews a lot of info into the log). 6. At the Blue Ocean UI all fails in parallel steps seem to be grouped to the very bottom half of the screen, after 150+ of successfully executed tests. Since these are mostly in the order they're being started (I assume), it's making me believe, that it might be somehow related to either GC taking a lot of time or some memory leaking here and there. A grand total would be of 5-10 tests of 300+ randomly crashing, and almost always the annoying java.lang.interruptedException with the whole run (That took 3-4 days to complete!) just freezing. A full regression that takes a few days to complete almost always triggers the bug. I'm willing to help solve this issue, but since it requires some sacred knowledge about jenkins' guts I do not have, I can either post my pipeline script (which will most likely be useless, due to a huge amount of our internal tools being
[JIRA] (JENKINS-53732) Git plugin unit test is leaking into user's git config
Title: Message Title
Joseph Petersen updated an issue
Jenkins / JENKINS-53732
Git plugin unit test is leaking into user's git config
Change By:
Joseph Petersen
I have had several times where I noticed my user.email and user.name was changed in my git config. This is the culprit: https://github.com/jenkinsci/git-plugin/blob/70634f15702157af3a5b7f49e953882c45e438df/src/test/java/jenkins/plugins/git/CliGitCommand.java#L137-L149 {code:java}[include] path = .gitconfig.local[user] name = Name From Git-Plugin-Test email = email.from.git.plugin.t...@example.com{code} Because I use a include of local git global config.Finally figured out it was git-plugin unit tests messing with my config. Is there are way we can ban the test or fix this for all versions since this test was included. Happens for instance when you run unit test for Bitbucket branch source 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-53732) Git plugin unit test is leaking into user's git config
Title: Message Title
Joseph Petersen updated an issue
Jenkins / JENKINS-53732
Git plugin unit test is leaking into user's git config
Change By:
Joseph Petersen
I have had several times where I noticed my user.email and user.name was changed in my git config.This is the culprit: [ https://github.com/jenkinsci/git-plugin/blob/70634f15702157af3a5b7f49e953882c45e438df/src/test/java/jenkins/plugins/git/CliGitCommand.java#L137-L149 ] {code:java}[include] path = .gitconfig.local[user] name = Name From Git-Plugin-Test email = email.from.git.plugin.t...@example.com{code} Because I use a include of local git global config.Finally figured out it was git-plugin unit tests messing with my config. Is there are way we can ban the test or fix this for all versions since this test was included. Happens for instance when you run unit test for Bitbucket branch source 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-53732) Git plugin unit test is leaking into user's git config
Title: Message Title Joseph Petersen created an issue Jenkins / JENKINS-53732 Git plugin unit test is leaking into user's git config Issue Type: Task Assignee: Mark Waite Components: git-plugin Created: 2018-09-22 12:21 Priority: Blocker Reporter: Joseph Petersen I have had several times where I noticed my user.email and user.name was changed in my git config. [include] path = .gitconfig.local [user] name = Name From Git-Plugin-Test email = email.from.git.plugin.t...@example.com Because I use a include of local git global config. Finally figured out it was git-plugin unit tests messing with my config. Is there are way we can ban the test or fix this for all versions since this test was included. Add Comment
[JIRA] (JENKINS-53129) Parallel sequential stages in Blue Ocean showing wrong status with no Triggered Builds
Title: Message Title
Elie Kassis edited a comment on JENKINS-53129
Re: Parallel sequential stages in Blue Ocean showing wrong status with no Triggered Builds
I trigger jobs from inside the stage as shown below code sample.Noting that the {color:#de350b}*Triggered Builds*{color} section was working properly previously before you started allowing in Blue Ocean to display sequential stages inside a parallel one. +It is very important and crucial to see the Triggered Builds within a stage while PROCESSING and not just when the stage is DONE.+ {code:java}stage('Pushing 2 Tests and 2 Debug jobs') {//failFast truewhen { _expression_ { Push2TEs == 'true' }}parallel { stage('TE1') { stages { stage('PUSH TE1') {options { retry(2) timeout(time: 3, unit: 'HOURS')}steps { script { timestamps { println("${STAGE_BEGIN} PUSH TE1") def TE1build = build job: "TESTING/${TEST_LABEL1}/PAC_PTE/0010.TESTING-Headline",parameters: [ [$class: 'StringParameterValue', name: 'MX_VERSION', value: MX_VERSION], [$class: 'StringParameterValue', name: 'MX_CHANGELIST', value: MX_CHANGELIST], [$class: 'BooleanParameterValue', name: 'Execute_benchmark', value: true], [$class: 'BooleanParameterValue', name: 'Generate_traceability_reports', value: true], [$class: 'StringParameterValue', name: 'SETUPS', value: 'Custom'], [$class: 'StringParameterValue', name: 'Custom_Script_Before', value: '/nfs_qa_pac/pac-pte/jenkins/getEnvProperties.sh'], [$class: 'StringParameterValue', name: 'Custom_Script_After', value: '/nfs_qa_pac/pac-pte/jenkins/restoreEnv.sh']],propagate: false LogJobStatus("${TEST_LABEL1}", TE1build.result) currentBuild.result = TE1build.result } }} } stage('Archive Logs') {steps { script { timestamps { println("${STAGE_BEGIN} Archive ${TEST_LABEL1} Logs") //sleep time: 1, unit: 'MINUTES' def archiveLogsTE1 = build job: 'Archiving',parameters: [ [$class: 'StringParameterValue', name: 'BENCH_MARK_NAME', value: TE1_BENCH_MARK_NAME], [$class: 'StringParameterValue', name: 'VERSION', value: MX_VERSION], [$class: 'StringParameterValue', name: 'CHANGELIST', value: MX_CHANGELIST], [$class: 'StringParameterValue', name: 'APP_DIR', value: TE1_APP_DIR], [$class: 'StringParameterValue', name: 'RESULTS_DIR', value: TE1_LOG_DIR], [$class: 'StringParameterValue', name: 'KPI_DIR', value: TE1_WORKSPACE], [$class: 'StringParameterValue', name: 'TPK', value: TPK], [$class: 'StringParameterValue', name: 'JOB_ID', value: JOB_ID], [$class: 'StringParameterValue', name: 'TEST_ID', value: TEST_LABEL1], [$class: 'StringParameterValue', name: 'NODE', value: TE1_NODE]],propagate: false currentBuild.result = archiveLogsTE1.result LogJobStatus("Archive ${TEST_LABEL1} Logs", archiveLogsTE1.result) println("${STAGE_END} Archive ${TEST_LABEL1} Logs") } }} } } } stage('TE2') { stages { stage('PUSH TE2') {options { retry(2) timeout(time: 3, unit: 'HOURS')}steps { script { timestamps { println("${STAGE_BEGIN} PUSH TE2") def TE2build = build job: "TESTING/${TEST_LABEL2}/PAC_PTE/0010.TESTING-Headline",parameters: [
[JIRA] (JENKINS-53129) Parallel sequential stages in Blue Ocean showing wrong status with no Triggered Builds
Title: Message Title
Elie Kassis commented on JENKINS-53129
Re: Parallel sequential stages in Blue Ocean showing wrong status with no Triggered Builds
I trigger jobs from inside the stage as shown below code sample. Noting that the Triggered Builds section was working properly previously before you started allowing in Blue Ocean to display sequential stages inside a parallel one.
stage('Pushing 2 Tests and 2 Debug jobs') {
//failFast true
when {
_expression_ {
Push2TEs == 'true'
}
}
parallel { stage('TE1') {
stages {
stage('PUSH TE1') {
options {
retry(2)
timeout(time: 3, unit: 'HOURS')
}
steps {
script {
timestamps {
println("${STAGE_BEGIN} PUSH TE1")
def TE1build = build job: "TESTING/${TEST_LABEL1}/PAC_PTE/0010.TESTING-Headline",
parameters: [
[$class: 'StringParameterValue', name: 'MX_VERSION', value: MX_VERSION],
[$class: 'StringParameterValue', name: 'MX_CHANGELIST', value: MX_CHANGELIST],
[$class: 'BooleanParameterValue', name: 'Execute_benchmark', value: true],
[$class: 'BooleanParameterValue', name: 'Generate_traceability_reports', value: true],
[$class: 'StringParameterValue', name: 'SETUPS', value: 'Custom'],
[$class: 'StringParameterValue', name: 'Custom_Script_Before', value: '/nfs_qa_pac/pac-pte/jenkins/getEnvProperties.sh'],
[$class: 'StringParameterValue', name: 'Custom_Script_After', value: '/nfs_qa_pac/pac-pte/jenkins/restoreEnv.sh']
],
propagate: false
LogJobStatus("${TEST_LABEL1}", TE1build.result)
currentBuild.result = TE1build.result
}
}
}
}
stage('Archive Logs') {
steps {
script {
timestamps {
println("${STAGE_BEGIN} Archive ${TEST_LABEL1} Logs")
//sleep time: 1, unit: 'MINUTES'
def archiveLogsTE1 = build job: 'Archiving',
parameters: [
[$class: 'StringParameterValue', name: 'BENCH_MARK_NAME', value: TE1_BENCH_MARK_NAME],
[$class: 'StringParameterValue', name: 'VERSION', value: MX_VERSION],
[$class: 'StringParameterValue', name: 'CHANGELIST', value: MX_CHANGELIST],
[$class: 'StringParameterValue', name: 'APP_DIR', value: TE1_APP_DIR],
[$class: 'StringParameterValue', name: 'RESULTS_DIR', value: TE1_LOG_DIR],
[$class: 'StringParameterValue', name: 'KPI_DIR', value: TE1_WORKSPACE],
[$class: 'StringParameterValue', name: 'TPK', value: TPK],
[$class: 'StringParameterValue', name: 'JOB_ID', value: JOB_ID],
[$class: 'StringParameterValue', name: 'TEST_ID', value: TEST_LABEL1],
[$class: 'StringParameterValue', name: 'NODE', value: TE1_NODE]
],
propagate: false
currentBuild.result = archiveLogsTE1.result
LogJobStatus("Archive ${TEST_LABEL1} Logs", archiveLogsTE1.result) println("${STAGE_END} Archive ${TEST_LABEL1} Logs")
}
}
}
}
}
} stage('TE2') {
stages {
stage('PUSH TE2') {
options {
retry(2)
timeout(time: 3, unit: 'HOURS')
}
steps {
script {
timestamps {
println("${STAGE_BEGIN} PUSH TE2")
def TE2build = build
[JIRA] (JENKINS-53129) Parallel sequential stages in Blue Ocean showing wrong status with no Triggered Builds
Title: Message Title Olivier Lamy edited a comment on JENKINS-53129 Re: Parallel sequential stages in Blue Ocean showing wrong status with no Triggered Builds *Triggered Builds but* how do you trigger the job jobs ? 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-53129) Parallel sequential stages in Blue Ocean showing wrong status with no Triggered Builds
Title: Message Title Olivier Lamy commented on JENKINS-53129 Re: Parallel sequential stages in Blue Ocean showing wrong status with no Triggered Builds how do you trigger the job? 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-53129) Parallel sequential stages in Blue Ocean showing wrong status with no Triggered Builds
Title: Message Title Elie Kassis updated an issue Jenkins / JENKINS-53129 Parallel sequential stages in Blue Ocean showing wrong status with no Triggered Builds Change By: Elie Kassis Summary: Parallel sequential stages in Blue Ocean showing wrong status with no Triggered Builds 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-53129) Parallel stages in Blue Ocean showing wrong status
Title: Message Title Elie Kassis updated JENKINS-53129 Jenkins / JENKINS-53129 Parallel stages in Blue Ocean showing wrong status Change By: Elie Kassis Status: Fixed but Unreleased Reopened 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-53129) Parallel stages in Blue Ocean showing wrong status
Title: Message Title
Elie Kassis edited a comment on JENKINS-53129
Re: Parallel stages in Blue Ocean showing wrong status
[~olamy] the status issue was resolved with your last fix (Blue Ocean 1.8.3)(Jenkins 2.138.1), but the {color:#de350b}*Triggered Builds*{color} Section is not appearing when having processing stage. The Triggered Build section is only appearing when the stage is done.In addition when having several parallel stages processing at the same time, only 1 of the stages is having the blue circle with the blue dot blinking inside.Can you please check?!image-2018-09-22-13-17-53-432.png|width=465,height=237!
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-53129) Parallel stages in Blue Ocean showing wrong status
Title: Message Title
Elie Kassis edited a comment on JENKINS-53129
Re: Parallel stages in Blue Ocean showing wrong status
[~olamy] the status issue was resolved with your last fix (Blue Ocean 1.8.3)(Jenkins 2.138.1), but the {color:#de350b}*Triggered Builds*{color} Section is not appearing when having processing stage. The Triggered Build section is only appearing when the stage is done.In addition when having several parallel stages processing at the same time, only 1 of the stages is having the blue circle with the blue dot blinking inside. Can you please check?!image-2018-09-22-13-17-53-432.png|width=465,height=237!
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-53731) Include jackson-annotations
Title: Message Title Nikolas Falco edited a comment on JENKINS-53731 Re: Include jackson-annotations My fault, my points to the code had import jackson 1 package annotations, this was the reason I suppose the jar was not included in this plugin.I'm sorry. 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-53731) Include jackson-annotations
Title: Message Title Nikolas Falco closed an issue as Done My fault, my points to the jackson 1 package annotations, this was the reason I suppose the jar was not included in this plugin. I'm sorry. Jenkins / JENKINS-53731 Include jackson-annotations Change By: Nikolas Falco Status: Open Closed Resolution: Done 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-53731) Include jackson-annotations
Title: Message Title Nikolas Falco created an issue Jenkins / JENKINS-53731 Include jackson-annotations Issue Type: New Feature Assignee: Devin Nusbaum Components: jackson2-api-plugin Created: 2018-09-22 10:36 Priority: Major Reporter: Nikolas Falco Some plugins that have to parse response from REST has annotated its java bean with jackson annotation to make easier the mapping. These annotations are in a separate bundle jackson-annotations that is missing by this plugins (Jackson propetary annotations are more powerfull than JAXB, this also avoid migrate existing code) Add Comment
[JIRA] (JENKINS-53129) Parallel stages in Blue Ocean showing wrong status
Title: Message Title
Elie Kassis edited a comment on JENKINS-53129
Re: Parallel stages in Blue Ocean showing wrong status
[~olamy] the status issue was resolved with your last fix (Blue Ocean 1.8.3) (Jenkins 2.138.1) , but the {color:#de350b}*Triggered Builds*{color} Section is not appearing when having processing stage.Can you please check?!image-2018-09-22-13-17-53-432.png|width=465,height=237!
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-53129) Parallel stages in Blue Ocean showing wrong status
Title: Message Title
Elie Kassis edited a comment on JENKINS-53129
Re: Parallel stages in Blue Ocean showing wrong status
[~olamy] the status issue was resolved with your last fix (Blue Ocean 1.8.3) , but the {color:#de350b}*Triggered Builds*{color} Section is not appearing when having processing stage.Can you please check?!image-2018-09-22-13-17-53-432.png|width=465,height=237!
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-53129) Parallel stages in Blue Ocean showing wrong status
Title: Message Title Elie Kassis commented on JENKINS-53129 Re: Parallel stages in Blue Ocean showing wrong status Olivier Lamy the status issue was resolved with your last fix, but the Triggered Builds Section is not appearing when having processing stage. Can you please check? 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-53129) Parallel stages in Blue Ocean showing wrong status
Title: Message Title Elie Kassis updated an issue Jenkins / JENKINS-53129 Parallel stages in Blue Ocean showing wrong status Change By: Elie Kassis Attachment: image-2018-09-22-13-17-53-432.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-53730) Automatically reuse stashes in declerative pipelines
Title: Message Title Victor Bjelkholm created an issue Jenkins / JENKINS-53730 Automatically reuse stashes in declerative pipelines Issue Type: New Feature Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2018-09-22 09:45 Priority: Minor Reporter: Victor Bjelkholm With https://issues.jenkins-ci.org/browse/JENKINS-45455 in place and that it can retry pipelines from particular stages is great and saves a lot of time. What would be even greater would be the possibility to configure a declarative pipeline to automatically reuse previous stashes if some file has/hasn't changed. The way I imagine the feature to work is that you can give data for a `stash` call that it will use to either reuse a stash from the last successful run or compute it again. Not exactly sure how the syntax for this would look, but would need some way of declaring in the beginning of a stage what variable to look at before reusing a stash, and if needed, jumps ahead to a `unstash` call instead of stashing again. Add Comment
