[JIRA] (JENKINS-62007) "filePaths" filter is not working for "ref-update" (refUpdated)
Title: Message Title
S. Panchenko created an issue
Jenkins / JENKINS-62007
"filePaths" filter is not working for "ref-update" (refUpdated)
Issue Type:
Bug
Assignee:
rsandell
Components:
gerrit-trigger-plugin
Created:
2020-04-22 11:26
Environment:
Jenkins ver. 2.186 Gerrit-Trigger: 2.30.4 Pipeline: Groovy: 2.65 SCM API: 2.4.0 Pipeline: Step API: 2.22
Labels:
plugin
Priority:
Minor
Reporter:
S. Panchenko
Example of plugin configuration:
[
@gerrit(gerritProjects=[
{
branches=[{compareType=PLAIN, pattern=unstable}],
compareType=PLAIN,
disableStrictForbiddenFileVerification=false,
pattern=dev_manifest_project,
filePaths=[
{
compareType=PLAIN,
pattern=some_manifest.xml
}
]
}
],
serverName=gerrit.internal.com,
triggerOnEvents=[@refUpdated()]
)])
Found info in old thread:
Feb 24, 2014. When there is ref-updated the option to choose path is taken under consideration. It just not working for ref-update.
[JIRA] (JENKINS-59177) Add support for additional output values (e.g nexus arifact links) besides a boolean value
Title: Message Title
S. Panchenko updated an issue
Jenkins / JENKINS-59177
Add support for additional output values (e.g nexus arifact links) besides a boolean value
Change By:
S. Panchenko
Currently, the function *nexusArtifactUploader* returns only a boolean value (i.e. java.lang.Boolean). It might be a good idea to return additional information from the function other than a boolean value:{code}def result = nexusArtifactUploader(...)echo result.getOutputLinks() // --> https://my-nexus.com:443/repository/CoolRepo/com/my/platform/unstable_platform/161/unstable-release.zipecho result.getResult() // --> True if success{code} h6.WorkaroundTo get these links I have to parse Jenkins log:{code}while (! script. currentBuild.rawBuild.getLog(100).join("\n").contains("Uploaded:")) {echo "Waiting for NexusArtifactUploader ... \n" } {code}
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201614.1567409389000.4134.1567409580144%40Atlassian.JIRA.
[JIRA] (JENKINS-59177) Add support for additional output values (e.g nexus arifact links) besides a boolean value
Title: Message Title
S. Panchenko created an issue
Jenkins / JENKINS-59177
Add support for additional output values (e.g nexus arifact links) besides a boolean value
Issue Type:
Improvement
Assignee:
Suresh Kumar
Components:
nexus-artifact-uploader-plugin
Created:
2019-09-02 07:29
Environment:
Jenkins ver. 2.164.3 using groovy Pipeline 2.6 and NexusArtifactUploader 2.10
Labels:
plugin pipeline
Priority:
Minor
Reporter:
S. Panchenko
Currently, the function nexusArtifactUploader returns only a boolean value (i.e. java.lang.Boolean). It might be a good idea to return additional information from the function other than a boolean value:
def result = nexusArtifactUploader(...)
echo result.getOutputLinks() // --> https://my-nexus.com:443/repository/CoolRepo/com/my/platform/unstable_platform/161/unstable-release.zip
echo result.getResult() // --> True if success
Workaround To get these links I have to parse Jenkins log:
while (!script.currentBuild.rawBuild.getLog(100).join("\n").contains("Uploaded:")) {
echo "Waiting for NexusArtifactUploader ... \n"
}
[JIRA] (JENKINS-35265) Parameter showGraphs: true has no effect using Pipeline job
Title: Message Title S. Panchenko assigned an issue to Manuel Recena Soto Jenkins / JENKINS-35265 Parameter showGraphs: true has no effect using Pipeline job Change By: S. Panchenko Assignee: S. Panchenko Manuel Recena Soto 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170968.1464786107000.20032.1563962460663%40Atlassian.JIRA.
[JIRA] (JENKINS-45650) CLI known_hosts support fails on non-standard SSH ports
Title: Message Title
S. Panchenko edited a comment on JENKINS-45650
Re: CLI known_hosts support fails on non-standard SSH ports
[~giorgiosironi] (y) removing removing the offending key from my {{.ssh/known_hosts}} works for me. Thank you!
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183843.1500471216000.9317.1561551720843%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45650) CLI known_hosts support fails on non-standard SSH ports
Title: Message Title S. Panchenko commented on JENKINS-45650 Re: CLI known_hosts support fails on non-standard SSH ports Giorgio Sironi removing removing the offending key from my .ssh/known_hosts works for me. Thank you! 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183843.1500471216000.9307.1561551720717%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54657) dropWhile doesn't behave correctly
Title: Message Title
S. Panchenko commented on JENKINS-54657
Re: dropWhile doesn't behave correctly
Workaround: create NonCPS-function in a shared library:
@NonCPS
static dropWhileIfNotFound(final c, final search_item) {
return c.dropWhile{ it != search_item }
}
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195448.1542306982000.5382.1561108860281%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47641) FAILURE during Repository Connector build step
Title: Message Title S. Panchenko commented on JENKINS-47641 Re: FAILURE during Repository Connector build step Similar issue on Jenkins 2.164.3, Repository Connector 1.2.5, Nexus OSS 3.6.0-02. First of all I couldn't configure "Nexus Repository Manager Servers" (com.sonatype.nexus.api.zz.ey: Not Found), and in via Artifact Resolver: Repositories configuration (URL: https://my-nexus.com/repository/MyProjectSnapshots/, Repo type: hosted, Repo Id: MyProjectSnapshots) leads to: 16:18:55 INFO: define repo: [Repository id=MyProjectSnapshots, type=hosted, url="" isRepositoryManager=false]16:18:55 INFO: set authentication for jenkins.user*16:18:55* failed collecting dependency info for [Artifact com.foo.my:android-apps:::0.1-SNAPSHOT] ... Caused by: org.sonatype.aether.transfer.NoRepositoryConnectorException: No connector available to access repository MyProjectSnapshots (my-nexus.com/repository/MyProjectSnapshots) of type hosted using the available factories WagonRepositoryConnectorFactory Groovy code: artifactResolver artifacts: [artifact(artifactId: 'android-apps', classifier: '', extension: '', groupId: 'com.foo.my', targetFileName: '', version: '0.1-SNAPSHOT')], releaseChecksumPolicy: 'ignore', snapshotChecksumPolicy: 'ignore', targetDirectory: '.' In addition to I've tried different configurations: with\without extension, different URL format (with\without application port), with\without POM file, etc. For the record I've uploaded maven-artifacts by means of nexusArtifactUploader plugin, I could not find a way how to upload artifacts via Artifact Resolver but documentation says it has such feature. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this
[JIRA] (JENKINS-57105) "Stage logging" via clicking stage button similar as in pipeline diagram
Title: Message Title S. Panchenko created an issue Jenkins / JENKINS-57105 "Stage logging" via clicking stage button similar as in pipeline diagram Issue Type: Improvement Assignee: Paul Horvath Attachments: AggregatedPipeline.png, pWbux.png Components: pipeline-aggregator-view-plugin Created: 2019-04-18 09:36 Environment: Jenkins 2.164.2 Pipeline Aggregator View Plugin 1.8 Priority: Minor Reporter: S. Panchenko If you click on a stage in pipeline graph, then the button "Logs" appears, and then you can click on it, and see the "Stage log": It would be practical to have similar behavior in Pipeline Aggregator Plugin: Add Comment
[JIRA] (JENKINS-54481) [Pipeline Aggregator View] Stages cannot be clicked in
Title: Message Title S. Panchenko commented on JENKINS-54481 Re: [Pipeline Aggregator View] Stages cannot be clicked in Created 2 similar feature-requests: JENKINS-57105, JENKINS-57104 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-57104) "Interactive input" via clicking stage button similar as in pipeline diagram
Title: Message Title S. Panchenko updated an issue Jenkins / JENKINS-57104 "Interactive input" via clicking stage button similar as in pipeline diagram Change By: S. Panchenko If there is [interactive input|https://jenkins.io/doc/pipeline/steps/pipeline-input-step/] (i.e. Pipeline: Input Step), then the stage button has different color (or form) and the button becomes "clickable".!checkbox.png!User can select an option in Aggregator View Plugin, if there is [interactive input|https://jenkins.io/doc/pipeline/steps/pipeline-input-step/].!how_it_should_be.png! *Note*: if the feature is complex, we can break it into two tasks:- button visualization when [interactive input|https://jenkins.io/doc/pipeline/steps/pipeline-input-step/] exists- [interactive input|https://jenkins.io/doc/pipeline/steps/pipeline-input-step/] in Pipeline Aggregator View 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-57104) "Interactive input" via clicking stage button similar as in pipeline diagram
Title: Message Title S. Panchenko created an issue Jenkins / JENKINS-57104 "Interactive input" via clicking stage button similar as in pipeline diagram Issue Type: Improvement Assignee: Paul Horvath Attachments: checkbox.png, how_it_should_be.png Components: pipeline-aggregator-view-plugin Created: 2019-04-18 09:07 Environment: Jenkins 2.164.2 Pipeline Aggregator View Plugin 1.8 Priority: Minor Reporter: S. Panchenko If there is interactive input (i.e. Pipeline: Input Step), then the stage button has different color (or form) and the button becomes "clickable". User can select an option in Aggregator View Plugin, if there is interactive input. Add Comment
[JIRA] (JENKINS-54322) Add ability SKIP stage in script pipeline
Title: Message Title
S. Panchenko edited a comment on JENKINS-54322
Re: Add ability SKIP stage in script pipeline
I do agree with this proposal. In addition to, there is another reason. This should prevent against the error: {quote} "Scripts not permitted to use staticMethod org.jenkinsci.plugins.pipeline.modeldefinition.Utils markStageSkippedForConditional java.lang.String. Administrators can decide whether to approve or reject this signature. {quote} For another, this may duplicate JENKINS-37781
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-54322) Add ability SKIP stage in script pipeline
Title: Message Title S. Panchenko commented on JENKINS-54322 Re: Add ability SKIP stage in script pipeline I do agree with this proposal. In addition to, there is another reason. This should prevent against the error: "Scripts not permitted to use staticMethod org.jenkinsci.plugins.pipeline.modeldefinition.Utils markStageSkippedForConditional java.lang.String. Administrators can decide whether to approve or reject this signature. 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-56528) Gerrit trigger 2.29.0 does not trigger jobs
Title: Message Title S. Panchenko commented on JENKINS-56528 Re: Gerrit trigger 2.29.0 does not trigger jobs Confirmed on Jenkins ver. 2.164.1, Gerrit Trigger 2.29.0. We use groovy-pipeline and dynamicTriggerConfiguration: pipelineTriggers([gerrit(customUrl: '', dynamicTriggerConfiguration: true, gerritProjects: [[branches: [[compareType: 'PLAIN', pattern: '']], compareType: 'PLAIN', disableStrictForbiddenFileVerification: false, pattern: '']], serverName: 'some_server.com', triggerConfigURL: 'http://some_server.com/triggers.txt', triggerOnEvents: [patchsetCreated(excludeDrafts: false, excludeNoCodeChange: false, excludeTrivialRebase: false)])]) Re-trigger via +Query and Trigger Gerrit Patche+s doesn't help. Workaround: downgrading to Gerrit Trigge 2.28.0. 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-35265) Parameter showGraphs: true has no effect using Pipeline job
Title: Message Title
S. Panchenko commented on JENKINS-35265
Re: Parameter showGraphs: true has no effect using Pipeline job
The same issue: Build Pipeline Plugin 1.5.8, Jenkins ver. 2.150.1, Log Parser Plugin 2.0.
timestamps { node ("some_node") {
stage ('Build') { // ... }
stage ('Log Parser') {
step([$class: 'LogParserPublisher', projectRulePath: "../parse_rules", useProjectRule: true, showGraphs: true, unstableOnWarning: false, failBuildOnError: false])
}
}}
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-51593) Gerrit Trigger for Dynamic trigger configuration in Jenkins Pipeline script
Title: Message Title S. Panchenko commented on JENKINS-51593 Re: Gerrit Trigger for Dynamic trigger configuration in Jenkins Pipeline script Any update on this? or possible workaround? 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] [git-plugin] (JENKINS-27981) Impossible to clone git repo
Title: Message Title S. Panchenko commented on JENKINS-27981 Re: Impossible to clone git repo What was the environment variable you set? I'm having the same issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
