date:20170111

[JIRA] (JENKINS-41019) Check in into subfolder of current project

2017-01-11 Thread peter.si...@knorr-bremse.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Peter Simon created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41019  
 
 
  Check in into subfolder of current project   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 PTC ALM  
 
 
Components: 
 integrity-plugin  
 
 
Created: 
 2017/Jan/12 7:50 AM  
 
 
Environment: 
 Jenkins 2.32.1, PTC Integrity CM - Jenkins Plugin 2.0.2, Windows 7  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Peter Simon  
 

  
 
 
 
 

 
 Hello All, I am using the 2.0.2 version of this plugin. I'd like to check-in at the end of the build process. My workspace looks like this: -folder1 -folder2 --fileA -file1 -file2 The build output is folder2, and I'd like to check-in into that folder of the project. Currently if I set the: 
 
Build output folder to: folder2 
Includes filter: fileA 
 Then after the checkin process finishes, the fileA appears in the root of the project, not under the folder2. Is there any way with the current implementation to check in into a subfolder of the project? Can you help me with this? BR, Peter

[JIRA] (JENKINS-40894) setting not persistent for "ERRORLEVEL to set build unstable"

2017-01-11 Thread scm_issue_l...@java.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-40894  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: setting not persistent for "ERRORLEVEL to set build unstable"   
 

  
 
 
 
 

 
 Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/tasks/BatchFile.java core/src/main/java/hudson/tasks/Shell.java test/src/test/java/hudson/tasks/BatchFileTest.java test/src/test/java/hudson/tasks/ShellTest.java test/src/test/resources/hudson/tasks/BatchFileTest/canLoadUnstableReturnFromDisk.zip test/src/test/resources/hudson/tasks/ShellTest/canLoadUnstableReturnFromDisk.zip http://jenkins-ci.org/commit/jenkins/93467c3f4bc74172b41543eea13e6771916d435a Log: [FIX JENKINS-40894] Restore unstableReturn in readResolve  
 

  
 
 
 
 

 
 
 

 
 
 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-40886) Enable JNLP4 protocol by default

2017-01-11 Thread scm_issue_l...@java.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40886  
 
 
  Enable JNLP4 protocol by default   
 

  
 
 
 
 

 
Change By: 
 SCM/JIRA link daemon  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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-40886) Enable JNLP4 protocol by default

2017-01-11 Thread scm_issue_l...@java.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-40886  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Enable JNLP4 protocol by default   
 

  
 
 
 
 

 
 Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/jenkins/slaves/JnlpSlaveAgentProtocol4.java http://jenkins-ci.org/commit/jenkins/bc2aacc443ef1f59922a196540821068cffe7e8b Log: [FIXED JENKINS-40886] - Enable the JNLP4 protocol by default  
 

  
 
 
 
 

 
 
 

 
 
 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-40886) Enable JNLP4 protocol by default

2017-01-11 Thread scm_issue_l...@java.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-40886  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Enable JNLP4 protocol by default   
 

  
 
 
 
 

 
 Code changed in jenkins User: Daniel Beck Path: core/src/main/java/jenkins/slaves/JnlpSlaveAgentProtocol4.java http://jenkins-ci.org/commit/jenkins/0ecd909dab8d3e8034580882a4a55172a7a8409c Log: Merge pull request #2709 from oleg-nenashev/remoting/JENKINS-40886-enable [FIXED JENKINS-40886] - Enable the JNLP4 protocol by default Compare: https://github.com/jenkinsci/jenkins/compare/ea98a23659ae...0ecd909dab8d  
 

  
 
 
 
 

 
 
 

 
 
 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-40813) "Enable Security" Help text should provide better advice

2017-01-11 Thread scm_issue_l...@java.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-40813  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Enable Security" Help text should provide better advice   
 

  
 
 
 
 

 
 Code changed in jenkins User: Daniel Beck Path: core/src/main/resources/jenkins/diagnostics/SecurityIsOffMonitor/message.properties http://jenkins-ci.org/commit/jenkins/ea98a23659ae907c71408ba0f38afceb3aabad74 Log: Merge pull request #2713 from daniel-beck/SecurityIsOffMonitor-blurb JENKINS-40813 More strongly worded message on enabling security Compare: https://github.com/jenkinsci/jenkins/compare/522f1be6581e...ea98a23659ae  
 

  
 
 
 
 

 
 
 

 
 
 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-40813) "Enable Security" Help text should provide better advice

2017-01-11 Thread scm_issue_l...@java.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-40813  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Enable Security" Help text should provide better advice   
 

  
 
 
 
 

 
 Code changed in jenkins User: Daniel Beck Path: core/src/main/resources/hudson/security/GlobalSecurityConfiguration/help-useSecurity.html http://jenkins-ci.org/commit/jenkins/81c0f46ca5577918295541746083d757ea74eb22 Log: [FIX JENKINS-40813] Better message on 'Enable security' option  
 

  
 
 
 
 

 
 
 

 
 
 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-32744) Svn revisions not showing up in pipeline build

2017-01-11 Thread jon.s...@modelon.com (JIRA)

Title: Message Title

Jon Sten commented on JENKINS-32744

Re: Svn revisions not showing up in pipeline build

Well, I wouldn't say that it is per design considering that the behaviour differs from FreeStyle builds. I would say that it is a use-case where you can see the revision for a particular build regardless if there is a change or not, in fact I created this defect due to complains from users using the Jenkins services I'm managing. Cause without the revision entry, the only way I know how to get the information is to dig it out of the console output, which is rather cumbersome. In either cause, I would say that the behaviour should be the same in free style builds and pipeline builds. I do realise that there is a considerable number of issues open, unfortunately this one is important for our organisation, it is one of the issues holding of big scale migration to pipeline. Hopefully I will be able to make a pull request that fixes this issue some day.

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.

1 2 3 4 >

1 - 100 of 326 matches

Mail list logo