Hi,
I am looking at the Plugin Manager im my jenkins 2.303.1 installation and it
shows this warning for the Pipeline: Nodes and Processes plugin:
Warning: The new version of this plugin is marked as incompatible with the
installed version. This is usually the case because its behavior
In Fedora terms, jenkins is a so called legacy service. It does not provide a
service file, but an old style System V init script.
That should be recognized by systemd, but for doing so, AFAIK it needs a
package called initscripts. Maybe that one is missing
on your system?
Cheers
-Fritz
On
Most likely, you have some plugins missing on the destination jenkins. To find
out, if some build step is provided by a plugin,
on the old jenkins, open the job configuration, find the step that is missing
on the destination and click on the help button
at the right side (hopefully it has one).
Replies inline
On 03.04.2017 00:08, Mark Waite wrote:
>
>
> On Sun, Apr 2, 2017 at 3:23 PM Fritz Elfert <fr...@fritz-elfert.de
> <mailto:fr...@fritz-elfert.de>> wrote:
>
> On 02.04.2017 22:35, Mark Waite wrote:
> > That message usually means
On 02.04.2017 22:35, Mark Waite wrote:
> That message usually means that the repository in the workspace does not
> contain a reference named "master" or named "origin/master". That is a
> surprise, since most repositories include a master branch.
If the git plugin has this requirement, then
On 16.03.2017 16:32, Ali Bazlamit wrote:
> Thanks Fritz for answering,
>
> Just to make sure i understood you good, i need to add the provider
> (profitbricks-rest) dependency to the pom.xml ?
>
Exactly. Well, first you fork the jclouds plugin. But I assume you are
familiar with the common
Hi,
I'm the current maintainer of the jclouds plugin.
It normally debends on jclouds-allcompute which should include all
official jclouds providers. Since your provider is still in the "labs"
category, it is therefore not available. Just add the necessary
dependency to
Replies inline ...
On 03.03.2017 12:04, Syed Shadab wrote:
> Hi
>
> I have installed jenkins via java -jar jenkins but its is not getting
> started. But same war is working fine on other server. I have
> highlighted the difference in RED what is the difference between logs
> where it is working
When executing a shell, jenkins uses the exit code for determining
success/failure. So:
=> Change your shell script so that it exits with an non-zero exitcode
in case of failure.
CU
-Fritz
On 04.02.2017 07:45, ssitaramasas...@gmail.com wrote:
> Hi,
>
> I have Jenkins running as Container in
On 22.01.2017 12:10, Flavio B wrote:
> Hello all,
>
> I'm performing the first jenkins setup in a firewalled environment.
> In order to be able to reach jenkins update site, I added a rule that
> allows me to go to http://updates.jenkins-ci.org/ via both http and https.
>
> The first time I
On 15.11.2016 17:26, Fritz Elfert wrote:
> most likely somewhere else than with *your* user account. Therefore do
> the following on your jenkins master:
>
> 1. sudo -i
> 2. su - jenkins
>(or whatever your jenkins user is named on the master)
> 3. ssh rhelhost
>(o
On 15.11.2016 15:14, Peter Berghold wrote:
> wish that were the case. Nope: running the same command from the
> command line yields the results I'm after. Since the script runs as
> tomcat8 and tomcat8 is trusted between the hosts I'm at a complete loss
> as to why this is happening.
Really?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/03/2014 02:23 PM, varun srivastava wrote:
Not really a jenkins question. More like a generic Unix question:
How to share certain directories or files between different users,
where each user shall be able to write/delete
Solution:
That's what
problem in LTS 1.532.1
Regards,
Harald
http://jenkins-ci.org/
2013/12/20 Fritz Elfert fr...@fritz-elfert.de
mailto:fr...@fritz-elfert.de
On 12/20/2013 10:01 AM, Fritz Elfert wrote:
Hi,
Did anybody else experience this?
Since update to Jenkins v1.544, we get hit by two errors: 1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Did anybody else experience this?
Since update to Jenkins v1.544, we get hit by two errors:
1. Whenever we save some job configuration, the notification-email
adress is emptied and can not be stored again.
2. A subsequent run of that job then
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/20/2013 10:01 AM, Fritz Elfert wrote:
Hi,
Did anybody else experience this?
Since update to Jenkins v1.544, we get hit by two errors: 1.
Whenever we save some job configuration, the notification-email
adress is emptied and can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
In the global config, the SVN workspace version can be selected. However
I have a mix of older/newer slave where some use 1.7 natively and some
others use still 1.6. I can't find any way to select the workspace
version per slave - which is a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Michael,
On 08/03/2012 10:00 PM, Michael Pailloncy wrote:
Le 03/08/2012 21:30, Fritz Elfert a écrit :
I can't find any way to select the workspace
version per slave
Hi,
I'm not sure to clearly understand what you want.
If you have slaves
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/03/2012 11:44 PM, Michael Pailloncy wrote:
[...]
In the meantime, I found out that there's an issue for this in JIRA
already:
https://issues.jenkins-ci.org/browse/JENKINS-14157
Unfortunately, it's still unassigned.
So you can use the
19 matches
Mail list logo
