[JIRA] (JENKINS-34981) Make valgrind-plugin compatible with pipeline

2018-03-07 Thread zet...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Seba Pien commented on  JENKINS-34981  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make valgrind-plugin compatible with pipeline
 

  
 
 
 
 

 
 Grerat news!  
 

  
 
 
 
 

 
 
 

 
 
 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-45650) CLI known_hosts support fails on non-standard SSH ports

2018-03-27 Thread zet...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Seba Pien commented on  JENKINS-45650  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: CLI known_hosts support fails on non-standard SSH ports   
 

  
 
 
 
 

 
 Hi   I'm using Jenkins ver 2.107.1 and this issue is still present.   /Seba  
 

  
 
 
 
 

 
 
 

 
 
 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-34981) Make valgrind-plugin compatible with pipeline

2018-03-21 Thread zet...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Seba Pien commented on  JENKINS-34981  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make valgrind-plugin compatible with pipeline
 

  
 
 
 
 

 
 How to use it?  
 

  
 
 
 
 

 
 
 

 
 
 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-18500) SCM-Sync stops synchronising after deleting a job

2018-09-19 Thread zet...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zeton commented on  JENKINS-18500  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SCM-Sync stops synchronising after deleting a job   
 

  
 
 
 
 

 
 Hi,   Workaround create Jenkins Job Free type:   Restrict where this project can be run: master   Execute shell command:  cd $JENKINS_HOME/scm-sync-configuration/checkoutConfiguration/     git status git add . git commit -m "Fix synchronisation"  git push  
 

  
 
 
 
 

 
 
 

 
 
 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-15128) Renaming job doesn't work with Git

2018-09-19 Thread zet...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zeton edited a comment on  JENKINS-15128  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Renaming job doesn't work with Git   
 

  
 
 
 
 

 
 Hi [~kylejw], Your solution fix issue. I even create job that runs on master to fix it:Jenkins Job Free type: Restrict where this project can be run: master Execute shell command: cd $JENKINS_HOME/scm-sync-configuration/checkoutConfiguration/    git statusgit  add .git  commit -m "Fix synchronisation"  .   git push     
 

  
 
 
 
 

 
 
 

 
 
 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-50792) Overall Admin access is required to create/copy a job, which wasn't required earlier

2018-09-19 Thread zet...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Seba Pien commented on  JENKINS-50792  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Overall Admin access is required to create/copy a job, which wasn't required earlier   
 

  
 
 
 
 

 
 It's still not resolved with JENKINS-49744.. I still see Also: hudson.security.AccessDeniedException2:U USER is missing the Overall/Administer permission at hudson.security.ACL.checkPermission(ACL.java:73) when cloning job. Jenkins ver. 2.138.1  
 

  
 
 
 
 

 
 
 

 
 
 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-50792) Overall Admin access is required to create/copy a job, which wasn't required earlier

2018-09-19 Thread zet...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Seba Pien reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50792  
 
 
  Overall Admin access is required to create/copy a job, which wasn't required earlier   
 

  
 
 
 
 

 
Change By: 
 Seba Pien  
 
 
Resolution: 
 Duplicate  
 
 
Status: 
 Resolved 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-15128) Renaming job doesn't work with Git

2018-09-19 Thread zet...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zeton commented on  JENKINS-15128  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Renaming job doesn't work with Git   
 

  
 
 
 
 

 
 Hi Kyle W,   Your solution fix issue. I even create job that runs on master to fix it: Jenkins Job Free type:   Restrict where this project can be run: master   Execute shell command:  cd $JENKINS_HOME/scm-sync-configuration/checkoutConfiguration/ git status git commit -m "Fix synchronisation" . git push      
 

  
 
 
 
 

 
 
 

 
 
 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-53606) SafeRestart Exception

2018-09-17 Thread zet...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Seba Pien created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53606  
 
 
  SafeRestart Exception   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2018-09-17 08:58  
 
 
Environment: 
  Jenkins 2.138.1 RHEL 7.2 x86_64  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Seba Pien  
 

  
 
 
 
 

 
 Hi,   After upgrading to latest LTS 2.138.1 restart and safe restart are throwing Exceptions. SafeRestart in UI is showing: "Jenkins cannot restart itself as currently configured." Command line:  JANKINS_url -ssh -user CoreID safe-restart ERROR: Unexpected exception occurred while performing safe-restart command. java.lang.NoClassDefFoundError: Could not initialize class com.sun.akuma.CLibrary at com.sun.akuma.JavaVMArguments.resolvePID(JavaVMArguments.java:128) at com.sun.akuma.JavaVMArguments.ofLinux(JavaVMArguments.java:116) at com.sun.akuma.JavaVMArguments.of(JavaVMArguments.java:104) at com.sun.akuma.JavaVMArguments.current(JavaVMArguments.java:92) at hudson.lifecycle.UnixLifecycle.(UnixLifecycle.java:55) at hudson.lifecycle.Lifecycle.get(Lifecycle.java:94) at jenkins.model.Jenkins.getLifecycle(Jenkins.java:2538) at org.jenkins.ci.plugins.saferestart.JenkinsUtils.canRestart(JenkinsUtils.java:37) at org.jenkins.ci.plugins.saferestart.SafeRestartRootAction.getIconFileName(SafeRestartRootAction.java:47) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at 

[JIRA] (JENKINS-53606) SafeRestart Exception

2018-09-17 Thread zet...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Seba Pien updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53606  
 
 
  SafeRestart Exception   
 

  
 
 
 
 

 
Change By: 
 Seba Pien  
 
 
Labels: 
 OpenJDK  
 

  
 
 
 
 

 
 
 

 
 
 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.