User Tools
toolsandtechnologies:jenkins_2
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| toolsandtechnologies:jenkins_2 [2023/03/31 18:29] – [Integration to BitBucket] - updated aryan | toolsandtechnologies:jenkins_2 [2023/06/07 17:39] (current) – [Artifactory storage] - fix url redirect aryan | ||
|---|---|---|---|
| Line 124: | Line 124: | ||
| } | } | ||
| </ | </ | ||
| + | |||
| + | ===== Artifactory storage ===== | ||
| + | |||
| + | Artifactory configuration is covered [[development: | ||
| + | |||
| + | Each pipeline has a step to push the build suite (war/jar, pom, XML etc) to the artifactory store in [[http:// | ||
| + | |||
| + | Ideally (as of June 6th, 2023 not working) we should keep | ||
| + | |||
| + | *- 15 days of IDMS & AUTO | ||
| + | *- 30 days of SUPPORT | ||
| + | *- Last 4 REL- | ||
| + | |||
| + | Deployment is covered via | ||
| + | < | ||
| + | stage (' | ||
| + | steps { | ||
| + | nexusPublisher( | ||
| + | nexusInstanceId: | ||
| + | nexusRepositoryId: | ||
| + | packages: [ | ||
| + | [$class: ' | ||
| + | | ||
| + | | ||
| + | ], | ||
| + | | ||
| + | ] | ||
| + | ] | ||
| + | ) | ||
| + | } | ||
| + | } | ||
| + | </ | ||
| + | |||
| + | The deployment playbooks should then source the artefact from the repo and not from our dev jenkins with a public IP interface (security risk). | ||
| + | |||
| + | |||
| + | |||
| + | |||
| ===== Generating API token (e.g. for Ansible) ===== | ===== Generating API token (e.g. for Ansible) ===== | ||
toolsandtechnologies/jenkins_2.1680283744.txt.gz · Last modified: 2023/03/31 18:29 by aryan
Page Tools
