You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The catalog for this code would build, whether or not the `exec { 'execute /usr/local/bin/some-script.sh': ... }` resource was part of the catalog. However, when the catalog is applied on the Puppet agent, it would fail if this resource is missing.
23
23
24
-
With the `--validate-references` command line flag (or the `settings[:validate_references]`[configuration setting](/doc/configuration.md), you can instruct `octocatalog-diff` to confirm that any resource targeted by a `before`, `notify`, `require`, and `subscribe` parameter actually exists. If the resource is missing from the catalog, an error will be raised, just as if the catalog failed to compile.
24
+
With the `--validate-references` command line flag (or the `settings[:validate_references]`[configuration setting](/doc/configuration.md)), you can instruct `octocatalog-diff` to confirm that any resource targeted by a `before`, `notify`, `require`, and `subscribe` parameter actually exists. If the resource is missing from the catalog, an error will be raised, just as if the catalog failed to compile.
Copy file name to clipboardExpand all lines: doc/dev/releasing.md
+40-2Lines changed: 40 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,8 +2,47 @@
2
2
3
3
The project maintainers are responsible for bumping the version number, regenerating auto-generated documentation, tagging the release, and uploading to rubygems.
4
4
5
-
0. Ensure that all changes have been merged to master.
5
+
## Local testing
6
+
7
+
To test the new version of `octocatalog-diff` in the Puppet repository:
8
+
9
+
0. In the Puppet checkout, start a new branch based off master.
10
+
0. In the `octocatalog-diff` checkout:
11
+
- Ensure that the desired branch is checked out.
12
+
- Choose a unique internal version number which has never been used in CI. A good guideline is that if you're planning to release a version `0.6.0` then for these tests, use `0.6.0a`, `0.6.0b`, ...
13
+
- Build the gem using your internal version number:
0. Back in the Puppet checkout, ensure that the changes are as expected (updates to Gemfile / Gemfile.lock, addition of new gem). Push the change and build appropriate CI job(s) to validate the changes.
25
+
26
+
## Merging
27
+
6
28
0. If necessary, complete a Pull Request to update the [version file](/.version).
29
+
0. If necessary, auto-generate the build documentation.
30
+
31
+
```
32
+
rake doc:build
33
+
```
34
+
35
+
0. Ensure that CI tests are all passing.
36
+
0. Merge and delete the branch.
37
+
38
+
## Releasing
39
+
40
+
Generally, a new release will correspond to a merge to master of one or more Pull Requests.
41
+
42
+
0. Ensure that all changes associated with the release have been merged to master.
43
+
- Merge all Pull Requests associated with release.
44
+
- If necessary, complete a Pull Request to update the [change log](/doc/CHANGELOG.md).
45
+
- If necessary (for significant changes), complete a Pull Request to update the top-level README file.
7
46
0. Ensure the the master branch is checked out on your system.
8
47
0. Run the release procedure:
9
48
@@ -13,7 +52,6 @@ The project maintainers are responsible for bumping the version number, regenera
13
52
14
53
This rake task handles the following:
15
54
16
-
- Auto-generates the [options reference](/doc/optionsref.md) (`rake doc:build`)
17
55
- Build the gem file (`rake gem:build`)
18
56
- Tag the release in the repository (`rake gem:tag`)
19
57
- Upload the gem file to rubygems (`rake gem:push`)
When we are assisting with troubleshooting, or implementing a feature you've requested, we may ask you to run `octocatalog-diff` from a non-master branch to try it out.
4
+
5
+
This document is intended for people who may not be familiar with git, GitHub, and/or ruby. If you already know how to do this in another way, feel free!
6
+
7
+
## Installation
8
+
9
+
1. Determine the branch name. If there's an open Pull Request, you can see the branch name near the top of the page.
3. Change into the directory created by your checkout:
21
+
22
+
```
23
+
cd $HOME/octocatalog-diff
24
+
```
25
+
26
+
4. Check out the branch you wish to use, filling in the branch name you determined in the first step:
27
+
28
+
```
29
+
git checkout BRANCH_NAME_FROM_STEP_1
30
+
```
31
+
32
+
5. Bootstrap the repository to pull in dependencies:
33
+
34
+
```
35
+
./script/bootstrap
36
+
```
37
+
38
+
6. Optional but recommended - run the test suite:
39
+
40
+
```
41
+
rake
42
+
```
43
+
44
+
## Use
45
+
46
+
Now that you have `octocatalog-diff` checked out and bootstrapped, it's time to use it.
47
+
48
+
We've created a wrapper script to make this easier for you.
49
+
50
+
1. Change directories to the location where you ordinarily run `octocatalog-diff` (for example: in your Puppet repository).
51
+
52
+
```
53
+
cd /etc/puppetlabs/code
54
+
```
55
+
56
+
2. Run the `script/octocatalog-diff-wrapper` script from *this* checkout. For example, if you checked out `octocatalog-diff` to your home directory, you could use:
Copy file name to clipboardExpand all lines: doc/installation.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,3 +47,9 @@ To install from source, you'll need a git client and internet access.
47
47
Note: If tests fail on your machine with a clean checkout of the master branch, we would definitely appreciate if you would report it. Please [open an issue](https://github.com/github/octocatalog-diff/issues/new) with the output and some information about your system (e.g. OS, ruby version, etc.) to let us know.
48
48
49
49
Once the code is downloaded and bootstrapped, please proceed to [Configuration](/doc/configuration.md).
50
+
51
+
## Running from an alternate branch
52
+
53
+
We have prepared specific instructions for running `octocatalog-diff` from a non-master branch, for testing changes that may be requested by the developers.
54
+
55
+
-[Running octocatalog-diff from a branch](/doc/dev/run-from-branch.md)
0 commit comments