Odd environment problem with git under Jenkins on AIX

[Rich Stephens]

I have finally gotten Jenkins and the git plugin running (I have managed to upgrade to Java8).

git works perfectly from the command line.

If I include /opt/freeware/lib into the LIBPATH when starting jenkins, when I try to connect to a remove repository, I get basically this error:

OpenSSL version mismatch. Built against 1000105f, you have 100000bf
fatal: Could not read from remote repository.

Please make sure you have the correct access rights

and the repository exists.

Coincidentally, this is the same error that I get if I include /opt/freeware/lib in my own LIBPATH.

If I _don't_ include /opt/freeware/lib in the LIBPATH for jenkins, I get:

Failed to connect to repository : Command "git ls-remote -h ssh://g...@stash.saas-p.com:7999/optio/core.git HEAD" returned status code 255:
stdout:
stderr: exec(): 0509-036 Cannot load program git because of the following errors:
0509-150   Dependent module /usr/lib/libiconv.a(libiconv.so.2) could not be loaded.
0509-152   Member libiconv.so.2 is not found in archive

If I don't include it in my own LIBPATH, git works normally.

I tried reproducing my own PATH and LIBPATH in the startup script for git, but still no joy.  I get the second error.


Obviously there is some sort of environment issue with jenkins, but I can't figure out what it is.
Any thoughts?

[Mark Waite]

Sorry, but no suggestions to offer on how to resolve that issue.

I would suggest that you host the Jenkins master on Linux or Windows and run an agent on AIX.  Running the master on AIX probably places you in the "less than 0.1% of all users" category.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/87b14e73-7fc1-49aa-b944-e227b473146c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Thanks!

Mark Waite

[Dirk Heinrichs]

Am Donnerstag, den 25.04.2019, 14:56 -0600 schrieb Mark Waite:

and run an agent on AIX

But wouldn't that still leave him with the env problem on that agent?

Unfortunately I don't have access to an AIX host anymore, so I'm afraid I also can't help.

Bye...

Dirk

-- 

Dirk Heinrichs

Senior Systems Engineer, Delivery Pipeline

OpenText ™ Discovery | Recommind

Phone: +49 2226 15966 18

Email: dhei...@opentext.com

Website: www.recommind.de

Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach

Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet.

[Rich Stephens]

I was thinking exactly the same thing.  I'd still have the same environment problem, either way.

[Mark Waite]

On Fri, Apr 26, 2019 at 6:06 AM Rich Stephens <rich...@gmail.com> wrote:

I was thinking exactly the same thing.  I'd still have the same environment problem, either way.

You might, but you won't have git commands executed to scan multibranch pipelines, since those are executed on the master.  

I assume that adjusting the environment of the agent is simpler and faster to test than adjusting the environment of the agent.  

Running the master on Linux (or Windows) allows you to use the same JDK that is used by many Jenkins users.  That will reduce the amount of code that might detect problems in the IBM JDK on AIX.  It was a preventive suggestion for future problems, with some distant hope that it might also assist with this specific issue.

 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/86743ecd-4ee4-4bcb-8b4e-b80c1586b76c%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Thanks!

Mark Waite

[Rich Stephens]

I fully have no clue what you just said.

"You might, but you won't have git commands executed to scan multibranch pipelines, since those are executed on the master."

Can you translate this to English?   Are you saying git won't run on the slave AT ALL?  If not, how will it get the source code to compile?

"I assume that adjusting the environment of the agent is simpler and faster to test than adjusting the environment of the agent." 

I assume you mean something else, because you just pretty much said that you assume apples are different from apples?

"Running the master on Linux (or Windows) allows you to use the same JDK that is used by many Jenkins users.  That will reduce the amount of code that might detect problems in the IBM JDK on AIX.  It was a preventive suggestion for future problems, with some distant hope that it might also assist with this specific issue."

I am running the same JDK (at least major/minor version) on all my Jenkins environments.  JDK 1.8. Including this AIX one. So...

[Dirk Heinrichs]

Am Freitag, den 26.04.2019, 06:20 -0700 schrieb Rich Stephens:

"You might, but you won't have git commands executed to scan multibranch pipelines, since those are executed on the master."

If you have Multibranch pipelines, they will scan your git repository for branches containing a Jenkinsfile and dynamically create jobs for each branch that meets this criteria. This happens on the master. The created jobs will then run on whatever agent is configured in the Jenkinsfile.

HTH...

[Rich Stephens]

Again, no clue what you're talking about.

Don't know what a "multibranch pipeline" is, and don't know what a Jenkinsfile is and why I would have it checked into my source code, nor how it applies to this situation at all?

[Rich Stephens]

OK, Googled "Jenkins multibranch pipeline" and "Jenkinsfile".   Still doesn't seem to have any bearing on my issue, but thanks for the input.

[Rich Stephens]

If anyone's still following this, my problem has been solved by simply switching the the "JGit" option for the Git plugin.  It's working perfectly.

Thanks for all who provided any information they could.

[Baptiste Mathus]

Le ven. 26 avr. 2019 à 15:20, Rich Stephens <rich...@gmail.com> a écrit :

I fully have no clue what you just said.

"You might, but you won't have git commands executed to scan multibranch pipelines, since those are executed on the master."

Can you translate this to English? 

Please, beware your phrasing. That is certainly not respectful in general, and even less to people trying to help you for free in their free time.

I suppose and hope that was just an expression misstep.

Thanks

[Rich Stephens]

It was a bit of a joke. I’m sorry if it offended you.
It didn’t seem to offend anyone actually involved in the conversation, but thanks for the tip.

[Mark Waite]

On Fri, Apr 26, 2019 at 2:28 PM Rich Stephens <rich...@gmail.com> wrote:

It was a bit of a joke.  I’m sorry if it offended you.
It didn’t seem to offend anyone actually involved in the conversation, but thanks for the tip.

That was the point where I decided to stop responding to the thread.  You seemed determined to proceed on the path that you had chosen.  That's your right, since it is your time that you're investing in your exploration.  

I am very interested to hear more about your experiences with Jenkins masters on AIX.  While the JDK on AIX is JDK 1.8, I believe it is using the IBM J9 virtual machine rather than the virtual machine provided by OpenJDK.  I expect many interesting discoveries await you in that exploration.  I'm aware of Jenkins agents on AIX and Jenkins agents on s390 mainframes (likely all running the IBM J9 virtual machine), but am not aware of any other users running a Jenkins master on AIX.

If you're interested in the history of the J9 virtual machine, refer to https://en.wikipedia.org/wiki/OpenJ9.  If you'd like to run a J9 virtual machine on commodity hardware, refer to https://adoptopenjdk.net/ where you can download an OpenJ9 based JDK.

If you'd like to join the Jenkins platform Special Interest Group, refer to https://jenkins.io/sigs/platform/ .  We'd love to have your help as we work with various platforms and explore various platforms.

Thanks!

Mark Waite

 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/900a6243-75d1-4cb4-bb75-63ee035e2335%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Thanks!

Mark Waite

[Rich Stephens]

Mark,

I am sincerely sorry if my sense of humor offended.   I'm not sure why you thought I was determined to proceed on any particular path.   I was willing to try the master/slave route as you suggested, and I asked a further question as to whether I would end up having the same problem on the slave - then I utterly failed to comprehend your answer.   My joke was at my own expense and my own failure to get what you were saying.

I sincerely appreciate your efforts to assist me.

I no longer require any help on this particular topic, however, since I have since been able to bypass the problem by using the "JGit" mode of the git plugin, which does not have the problem and has worked well so far.  Although I _am_ having one odd Java error getting thrown at the end of my builds (I have created a different post on this topic).   I have no idea if the problem would have happened using the native git open of the git plugin, or whether it's related to the JGit option, since I never got that far before.

As for my experiences using Jenkins master(s) on AIX, it is limited to this one machine, for the last 7 years.   It has been working fine using Java 1.6 and Jenkins 1.5(something?) for all of that.  It was using Mercurial as its source repository, and our Mercural server is being retired, so I was mandated to move my source code to git.   I then had to go through the process of upgrading Jenkins and Java so I could use the git plugin.  Thus begins my sad tale.

As for OpenJDK, that was actually my first choice for upgrading.  I searched all over the OpenJDK website for a link to a download for their JDK8 for AIX, and could not find it.  The page I _did_ find, however, mentioned that OpenJDK8 supports AIX 7.1 and later.  The machine I am working with is on AIX 6.1, and thus could not use the OpenJDK8 port for AIX even if I could have found it.   I cannot upgrade this machine to AIX 7.1.  I have to remain compatible to support AIX 6.1 because the software it is compiling is a legacy product for which my company still gets a decent amount of license revenue.

I would be happy to join the platform group, though I am not sure of what assistance I might be.  While I have used Jenkins on Linux, AIX, HPUX, and Windows, my experience is limited to simple master setups building a legacy C/C++ project.

Again, thank you for your assistance.

[Mark Waite]

On Tue, Apr 30, 2019 at 7:02 AM Rich Stephens wrote:

 

I would be happy to join the platform group, though I am not sure of what assistance I might be.  While I have used Jenkins on Linux, AIX, HPUX, and Windows, my experience is limited to simple master setups building a legacy C/C++ project.

Anyone with the skills to maintain an aging AIX environment will certainly be able to contribute when we're evaluating platform topics.  There are often interesting subtleties in using Jenkins on a different platform that can help the community as a whole.

Mark Waite

 

Again, thank you for your assistance.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c458b5e6-71aa-48a7-8fc9-cbdf4bcea6c6%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Thanks!

Mark Waite