[JIRA] (JENKINS-61587) don't create remote directory when there are no files to publish
Title: Message Title
Jimmy Praet commented on JENKINS-61587
Re: don't create remote directory when there are no files to publish
As a workaround I added execCommand: "rmdir -p --ignore-fail-on-non-empty ${remoteDirectory}"
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.205284.1584626952000.9885.1584696960056%40Atlassian.JIRA.
[JIRA] (JENKINS-61587) don't create remote directory when there are no files to publish
Title: Message Title Jimmy Praet created an issue Jenkins / JENKINS-61587 don't create remote directory when there are no files to publish Issue Type: Improvement Assignee: Unassigned Components: publish-over-ssh-plugin Created: 2020-03-19 14:09 Priority: Minor Reporter: Jimmy Praet We have a general build pipeline script that is reused by all our projects. It publishes some files to a documentation server with the sshPublisher step. But some projects don't have any documentation, and I would like to have no empty directory created for that project in that case. We see the following: SSH: Connecting from host [dc45dd1bbce5] SSH: Connecting with configuration [doc.cbss.inet] ... SSH: Disconnecting configuration [doc.cbss.inet] ... SSH: Transferred 0 file(s) So no files are transferred, but the configured remoteDirectory is still created, as specified in the documentation: remoteDirectory: Optional destination folder. This folder will be below the one in the global configuration, if present. The folder will be created if does not exist. I tried to specify makeEmptyDirs = false but that has no effect. I don't think that setting applies to the remoteDirectory.
[JIRA] (JENKINS-61587) don't create remote directory when there are no files to publish
Title: Message Title Jimmy Praet created an issue Jenkins / JENKINS-61587 don't create remote directory when there are no files to publish Issue Type: Improvement Assignee: Unassigned Components: publish-over-ssh-plugin Created: 2020-03-19 14:09 Priority: Minor Reporter: Jimmy Praet We have a general build pipeline script that is reused by all our projects. It publishes some files to a documentation server with the sshPublisher step. But some projects don't have any documentation, and I would like to have no empty directory created for that project in that case. We see the following: SSH: Connecting from host [dc45dd1bbce5] SSH: Connecting with configuration [doc.cbss.inet] ... SSH: Disconnecting configuration [doc.cbss.inet] ... SSH: Transferred 0 file(s) So no files are transferred, but the configured remoteDirectory is still created, as specified in the documentation: remoteDirectory: Optional destination folder. This folder will be below the one in the global configuration, if present. The folder will be created if does not exist. I tried to specify makeEmptyDirs = false but that has no effect. I don't think that setting applies to the remoteDirectory.
[JIRA] (JENKINS-48420) Provide lightweight checkout capability for Subversion
Title: Message Title Jimmy Praet commented on JENKINS-48420 Re: Provide lightweight checkout capability for Subversion Since upgrading to v2.12.x, our jenkins pipeline builds always showed "No changes". I configured -Djenkins.scm.impl.subversion.SubversionSCMFileSystem.disable=true as a 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] (JENKINS-50639) access WorkFlowRun status through the regular REST API
Title: Message Title Jimmy Praet created an issue Jenkins / JENKINS-50639 access WorkFlowRun status through the regular REST API Issue Type: Improvement Assignee: Sam Van Oort Components: pipeline-stage-view-plugin Created: 2018-04-06 15:44 Priority: Major Reporter: Jimmy Praet It is currently possible to obtain the status (e.g. PAUSED_PENDING_INPUT) of a org.jenkinsci.plugins.workflow.job.WorkflowRun via the new wfapi (https://github.com/jenkinsci/pipeline-stage-view-plugin/tree/master/rest-api). It would be nice if this could also be accessed through the regular jenkins REST API. So http://jenkins.io/job/my-pipeline/job/trunk/15/api/json instead of http://jenkins.io/job/my-pipeline/job/trunk/15/wfapi/ My use case is to get a global overview of all build statuses for a dashboard: http://jenkins.io/api/json?tree=views[name,url],jobs[name,url,buildable,scm[locations[remote]],builds[result,building,timestamp],jobs[name,url,buildable,description,builds[url,result,building,timestamp]]] The build result of a running pipeline job is null. So instead of the result, I would like
[JIRA] (JENKINS-49734) Use PauseAction while acquiring lock
Title: Message Title Jimmy Praet commented on JENKINS-49734 Re: Use PauseAction while acquiring lock Even if the lock was immediately available, it also shows as paused in the stage view though. 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-50034) duplicate links when report is overwritten
Title: Message Title Jimmy Praet created an issue Jenkins / JENKINS-50034 duplicate links when report is overwritten Issue Type: Improvement Assignee: Richard Bywater Attachments: image-2018-03-09-10-10-33-351.png Components: htmlpublisher-plugin Created: 2018-03-09 09:15 Priority: Minor Reporter: Jimmy Praet In our jenkins pipeline we regenerate a report with the same name multiple times. Specifically, it's a dependencies report that needs to be rechecked when the user elects to promote the artifact to staging / stable. The HTML publisher overwrites the report and only keeps the latest one. However, each time the same report is published, a new link is added to the build. They all point to the same report. Add Comment
[JIRA] (JENKINS-49186) non exportable objects exported causing errors in api/xml?depth=2
Title: Message Title Jimmy Praet commented on JENKINS-49186 Re: non exportable objects exported causing errors in api/xml?depth=2 I am also running into this issue with the JSON API. org.kohsuke.stapler.export.NotExportableException: class jenkins.scm.api.SCMHeadOrigin$Default doesn't have @ExportedBean 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-42696) configure jenkinsUrl with environment variable
Title: Message Title
Jimmy Praet created an issue
Jenkins / JENKINS-42696
configure jenkinsUrl with environment variable
Issue Type:
Improvement
Assignee:
Unassigned
Components:
core
Created:
2017/Mar/12 11:57 AM
Labels:
configuration environment-variables
Priority:
Minor
Reporter:
Jimmy Praet
It would be nice if the jenkinsUrl in jenkins.model.JenkinsLocationConfiguration.xml could be configured with an environment variable $ {JENKINS_URL} . This would make it easier to reuse an existing jenkins config directory when setting up a new jenkins server.
Add Comment
[JIRA] (JENKINS-41902) readMavenPom / writeMavenPom does not preserve comments and formatting
Title: Message Title Jimmy Praet created an issue Jenkins / JENKINS-41902 readMavenPom / writeMavenPom does not preserve comments and formatting Issue Type: Improvement Assignee: rsandell Components: pipeline-utility-steps-plugin Created: 2017/Feb/09 6:42 PM Labels: jenkins maven pom pipeline Priority: Major Reporter: Jimmy Praet When you use readMavenPom / writeMavenPom in a build pipeline, the comments and formatting of the pom.xml file are not preserved. Add Comment
[JIRA] (JENKINS-38887) support launching multibranch pipeline (branch indexing)
Title: Message Title Jimmy Praet created an issue Jenkins / JENKINS-38887 support launching multibranch pipeline (branch indexing) Issue Type: Improvement Assignee: Unassigned Components: pipeline-build-step-plugin Created: 2016/Oct/11 8:31 AM Priority: Minor Reporter: Jimmy Praet If you attempt to launch a multibranch pipeline with the build step, you get this error: ERROR: No parameterized job named xyz found It would be nice if this could trigger branch indexing of the multibranch pipeline. Add Comment
[JIRA] (JENKINS-38464) milestone step incorrectly detected as running inside parallel
Title: Message Title
Jimmy Praet created an issue
Jenkins / JENKINS-38464
milestone step incorrectly detected as running inside parallel
Issue Type:
Bug
Assignee:
Antonio Muñiz
Components:
pipeline-milestone-step-plugin
Created:
2016/Sep/23 10:18 AM
Priority:
Minor
Reporter:
Jimmy Praet
The following jenkins pipeline snippets results in "ERROR: Using a milestone step inside parallel is not allowed". But the milestone step is not used inside the parallel, it is outside.
parallel (
foo: {}, bar: {}
)
stage ('test') {
milestone 1
}
Add Comment
