|
|
|
|
|
|
Win a copy of Secure Financial Transactions with Ansible, Terraform, and OpenSCAP this week in the Cloud/Virtualization forum!
|
|
|
|
|
|
|
|
|
|
|
|
Stephan van Hulst wrote:
Do you mean how to get a password from environment specific configuration? Usually continuous deployment systems allow you to set environment variables for the system that the application will deploy to. You could configure the path to a configuration file where the password is located (or even configure the password itself) and then read it from the Java application.
How to do it exactly depends on the CI/CD system you're using.
The build-jre.sh script is used by a Jenkins pipeline script which in turn is used by the build-jres job to produce the following downloads:
Stephan van Hulst wrote:Uhh for what? Why do you want to build a JRE?
While it's hard to tell for certain, it sounds like you're referring to a script developed in-house by your current employer for their own internal use. Once that employer has dumped you out on the streets, you'll likely never see that script again. So there's no point in trying to learn anything about it.tangara goh wrote:I just want to take a small step to learn this shell script to build thing or automate stuff.
Some people, when well-known sources tell them that fire will burn them, don't put their hands in the fire.
Some people, being skeptical, will put their hands in the fire, get burned, and learn not to put their hands in the fire.
And some people, believing that they know better than well-known sources, will claim it's a lie, put their hands in the fire, and continue to scream it's a lie even as their hands burn down to charred stumps.
Tim Holloway wrote:
While it's hard to tell for certain, it sounds like you're referring to a script developed in-house by your current employer for their own internal use. Once that employer has dumped you out on the streets, you'll likely never see that script again. So there's no point in trying to learn anything about it.tangara goh wrote:I just want to take a small step to learn this shell script to build thing or automate stuff.
In the wider world, most Java apps are built using Maven, Ant or Gradle. Probably the most useful one to know at the moment is Maven, although that depends on what your next employer may prefer.
Beyond that, I don't know what CI CD means either, and Docker/containers are very different to build tools.
Oh. Come to think of it, I guess you mean Continuous Integration/Continous Deployment. That's a very broad topic and application building is only a very small part of it. Do try and avoid unexplained acronyms, though. IBM has at least one acronym I know of that has at least 4 different meanings and uses, depending on which of their products you're referring to and you probably wouldn't be able to guess any of them. And that's just in the IBM world.
1
Some people, when well-known sources tell them that fire will burn them, don't put their hands in the fire.
Some people, being skeptical, will put their hands in the fire, get burned, and learn not to put their hands in the fire.
And some people, believing that they know better than well-known sources, will claim it's a lie, put their hands in the fire, and continue to scream it's a lie even as their hands burn down to charred stumps.
1
1
Some people, when well-known sources tell them that fire will burn them, don't put their hands in the fire.
Some people, being skeptical, will put their hands in the fire, get burned, and learn not to put their hands in the fire.
And some people, believing that they know better than well-known sources, will claim it's a lie, put their hands in the fire, and continue to scream it's a lie even as their hands burn down to charred stumps.
|
Alas, poor Yorick, he knew this tiny ad:
SKIP - a book about connecting industrious people with elderly land owners
https://coderanch.com/t/skip-book
|
