<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Add info and test stages to pipeline :: Flywheel Data Labs - Workshops</title>
    <link>http://localhost:8080/ansible_f5/4.test/index.html</link>
    <description>Head back to the .gitlab-ci.yml file and edit the file again. This time add two new stages, one called info and one called test so that the stages section looks like the following:&#xA;stages: - registry - container - info - test Immediately following the stages section add the following to include some pre-built Gitlab testing tools:&#xA;include: - template: Security/SAST.gitlab-ci.yml - template: Jobs/SAST-IaC.gitlab-ci.yml - template: Security/Secret-Detection.gitlab-ci.yml sast: tags: - ansible_f5 kics-iac-sast: tags: - ansible_f5 secret_detection: tags: - ansible_f5</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 27 Mar 2024 10:40:21 -0400</lastBuildDate>
    <atom:link href="http://localhost:8080/ansible_f5/4.test/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Add info stage to pipeline</title>
      <link>http://localhost:8080/ansible_f5/4.test/get_info/index.html</link>
      <pubDate>Wed, 27 Mar 2024 10:40:21 -0400</pubDate>
      <guid>http://localhost:8080/ansible_f5/4.test/get_info/index.html</guid>
      <description>While still editing the .gitlab-ci.yml, add the following definition at the end of the file to define the info stage:&#xA;get_info: stage: info rules: - if: &#39;$CI_COMMIT_BRANCH == &#34;main&#34;&#39; when: always image: ${CI_REGISTRY}/${CI_PROJECT_PATH}/ansible:latest tags: - ansible_f5 script: - whoami - pip list - cat /etc/passwd - ansible --version - ls -al /home/ansible/.ssh - env allow_failure: true This is purely a debugging stage used during pipeline generation. It runs the ansible container image we created and then runs different commands from within the container to aid in troubleshooting.</description>
    </item>
    <item>
      <title>Add test stage to pipeline</title>
      <link>http://localhost:8080/ansible_f5/4.test/test_code/index.html</link>
      <pubDate>Wed, 27 Mar 2024 10:40:21 -0400</pubDate>
      <guid>http://localhost:8080/ansible_f5/4.test/test_code/index.html</guid>
      <description>Next copy the following block at the end to define the testing stage:&#xA;test_code: stage: test rules: - if: &#39;$CI_COMMIT_BRANCH == &#34;main&#34;&#39; when: always image: ${CI_REGISTRY}/${CI_PROJECT_PATH}/ansible:latest tags: - ansible_f5 script: - ansible --version allow_failure: false Commit the changes and browse back to the CI/CD pipeline and view the info and test stages after the container build completes. In the info stage select the get_info job to view the output from the env command. This shows all the different variables that Gitlab makes available to the CI/CD process by default. Many are used during this build configuration to make it modular and re-usable.</description>
    </item>
  </channel>
</rss>