u/Bodumin

I've been using the Needs Review option for pending transactions. It sticks even after it posts. I'll have to try it again but I think notes stick as well, I'll add a comment about what it was for or how I want to split the transaction.

When squished it should fit. Is squishing allowed though?

Uncheck include @library changes in job recent changes.

https://www.jenkins.io/doc/book/pipeline/shared-libraries/#retrieval-method

Are you seeing anything in the job log's or system logs https://www.jenkins.io/doc/book/system-administration/viewing-logs/

You can use a try/catch block

Below this catchError section is how to use try/catch with code examples https://www.jenkins.io/doc/pipeline/steps/workflow-basic-steps/#catcherror-catch-error-and-set-build-result-to-failure

I always have my team start with this docker tutorial from Hashicorp. There's 0 real setup, no need to deal with auth or remote state, no costs, and if you really mess everything up just run "docker rm" https://developer.hashicorp.com/terraform/tutorials/docker-get-started

https://plugins.jenkins.io/throttle-concurrents/

Can you clarify what the issue is? Provide logs of what is happening and explain what you think should happen.

You should provide details on how this is being done etc. Assuming you are using the plugins there is an option too exclude directories.

https://www.jenkins.io/doc/pipeline/steps/pipeline-utility-steps/#zip-create-zip-file

The formatting of your output isn't great but heres a guess. It's failing because it can't find a Jenkins method pylint. However since you are chmoding pylint above I assume it's there as a shell script. Wrap the action in sh() Ex sh(script: 'pylint fileme.py')

Have you installed docker on the host that is running Jenkins? Have you configured the plugin to use the docker host? The plugin is just an interface to docker, it doesn't install docker itself.

I number them sequentially. Server-1 server-2 etc

Whatever the default computer name is. Ours are in AWS so it's WIN-123456 (some random number)

You need to publish the udp port as well. Add -p 20000:20000/udp https://docs.docker.com/config/containers/container-networking/

If you want to focus on terraform I have Jr/new hires go through the docker doc's. It's a great way to setup and play with terraform without dealing with auth just yet and theres no bill. https://developer.hashicorp.com/terraform/tutorials/docker-get-started

For learning AWS+Terraform we use A Cloud Guru and their sandbox environments.

Where is the .env file being used? There may be other options depending on the technology.

WriteFile should work, are you getting errors you can share?

Unlikely it's the case here but we had builds starting randomly until we realized that changes to the library repo were being picked up and ran by the jobs that depended on the library.

Add a comma before script.

PowerShell(label: 'script label', script """Do-Thing -quick""")

The 5 minute timeout is configurable. We keep ours closer to a minute.

Depending on the order of those items means a few different things. We use Jenkins, running a job via docker agent with a terraform image to init/plan/apply It works well since state is remote, allows us to pin the terraform version and have multiple tasks running at the same time.

I'm in a similar role. Happy to help out as well if I can.

can you share your logs/job config. Jenkins should have failed because it doesn't know about the zip() method.

I've seen this where the controller has the dependencies cached but the new agent doesn't and can't reach bintray anymore. You'll have to update to use newer active cache servers https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/

It works fine. We have 6 different multi branch pipelines in one repo. Just need to name the pipeline files differently.

pass--destroy always to the kitchen command. This says that if kitchen is stopped to first destroy the resources.

We also run a lambda once a week that cleans up any running test kitchen instances in case they are missed somehow.