blsmith/dc-deployments-automation
1
0
Fork 0
mirror of https://bitbucket.org/atlassian/dc-deployments-automation.git synced 2025-12-14 00:43:06 -06:00
Code Issues Packages Projects Releases Wiki Activity

ITOPSENG-647 put product service file in the default path to allow systemctl mask and other linking operations to work properly

Browse Source
This commit is contained in:
Brett Meehan
2020-05-21 10:17:22 +10:00
parent 0fbc7609a1
commit 7b9e9e2328
5 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
DEVELOPMENT.md
View File

@@ -24,7 +24,7 @@ ways to do this; either directly if packaged, or via pip...
# Ubuntu 19.04+, Debian 10+
sudo apt-get install pipenv python-dev
# Older versions & RHEL/Amazon Linux, etc.
sudo apt-get install -y python-pip python-dev
# Or...
@@ -129,7 +129,7 @@ Some notable files and locations:
/var/log/ansible-bootstrap.log.
* The Jira installation is under /opt/atlassian/jira/<version>and symlinked to
/opt/atlassian/jira/current.
* The systemd service is configured in /etc/systemd/system/jira.service. Its
* The systemd service is configured in /usr/lib/systemd/system/jira.service. Its
stdout can be viewed with systemctl status jira.service and journalctl -u
jira.service.
* Other Tomcat logs can be located under /opt/atlassian/jira/current/logs/...
@@ -138,11 +138,11 @@ Some notable files and locations:
* This repository is configured to run tests on [bitbucket pipelines](https://bitbucket.org/atlassian/dc-deployments-automation/addon/pipelines/home).
* Pipeline definition is located in the [root of the repository](https://bitbucket.org/atlassian/dc-deployments-automation/src/master/bitbucket-pipelines.yml)
* Pipeline configuration is generated using Jinja2 and a simple python script. Pipeline generator is located [here](https://bitbucket.org/atlassian/dc-deployments-automation/src/master/pipeline_generator/)
* A pipeline configuration is generated by running the following make command
* A pipeline configuration is generated by running the following make command
```
make generate-pipeline > ../bitbucket-pipelines.yml
```
```
* [Molecule](https://molecule.readthedocs.io/en/stable/) tests are run in batches. A single test is run per batch to optimize for a faster dev feedback loop
* If you create a new role or add a new molecule scenario, then please ensure that you generate a new pipeline configuration by running the make command described above. If a new pipeline configuration is not generated, then the CI may not run any tests as it would fail at a pre-test validate stage.