-
Notifications
You must be signed in to change notification settings - Fork 46
Permalink
Loading
Choose a base ref
{{ refName }}
default
Loading
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: cloudfoundry/os-conf-release
base: v22.1.2
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: cloudfoundry/os-conf-release
compare: v22.1.3
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 14 commits
- 623 files changed
- 7 contributors
Commits on Oct 19, 2021
-
CF BOSH committed
Oct 19, 2021 Configuration menu - View commit details
-
Copy full SHA for 22d45d7 - Browse repository at this point
Copy the full SHA 22d45d7View commit details
Commits on Oct 29, 2021
-
Add auto-bumping for go dependencies
[#180054765] TAS-138 Add Golang autobumping and dependency autobumping to our Go repos
Configuration menu - View commit details
-
Copy full SHA for 020ab3d - Browse repository at this point
Copy the full SHA 020ab3dView commit details
Commits on Dec 9, 2021
-
🐞 Assume
systemd
is running; don't checkAs of Bionic & later, `systemd` is always running; we don't need to check for it in the pre-start script; it invites spurious errors. `systemd` replaces `init` (PID 1, the grandparent of all processes). It's the first process run, and it's always running, and you can't kill it, `-9` notwithstanding. Newer Bionic stemcells masquerade `systemd` as `/sbin/init` for backwards-compatibility. It also spawns a separate `systemd` later in the boot process. This introduces a race condition in our pre-start script, which checks if `systemd` is running: it doesn't always find a process named `systemd` This commit removes the check for `systemd`. Brian Cunnie assures, "`systemd` will _always_ be running." fixes: ``` Limits /tmp/build/bd5f12f4/os-conf-release/src/os-conf-acceptance-tests/limits_test.go:12 when limits are configured /tmp/build/bd5f12f4/os-conf-release/src/os-conf-acceptance-tests/limits_test.go:19 sets the limits for the systemd process [It] /tmp/build/bd5f12f4/os-conf-release/src/os-conf-acceptance-tests/limits_test.go:40 No future change is possible. Bailing out early after 1.918s. Got stuck at: os-conf/6ae65a92-263c-4f36-a70e-5dbeefc8963d: stderr | Jim was here. os-conf/6ae65a92-263c-4f36-a70e-5dbeefc8963d: stdout | 1024 os-conf/6ae65a92-263c-4f36-a70e-5dbeefc8963d: stderr | Connection to 10.0.0.4 closed. Waiting for: 60000 ``` Signed-off-by: Brian Cunnie <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for dd00681 - Browse repository at this point
Copy the full SHA dd00681View commit details
Commits on Apr 2, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 040ebdc - Browse repository at this point
Copy the full SHA 040ebdcView commit details
Commits on Jul 20, 2022
-
the harden sshd job wouldn't work on jammy because it uses a newer openssh version than 7. the initial commit that updated the behaviour to add trusty support see: 3d44807 on jammy that check (which I assume is checking that the minimum version is OpenSSH_7) fails and the property is not added. Update the check to parse out the major version and check if is greater than 6 which should keep trusty compability and work for future two digit major versions of OpenSSH. additionally the test deployments tried loading aufs which is shipped with jammy anymore. so loading it won't work either. switch to `lp` kernel module because lp is also used in the stemcell builder tests and is not only available in bionic and jammy but also in fips mode (which for this usecase doesn't matter). compare: cloudfoundry/bosh-linux-stemcell-builder@19b512a
nouseforaname committedJul 20, 2022 Configuration menu - View commit details
-
Copy full SHA for 87a9d02 - Browse repository at this point
Copy the full SHA 87a9d02View commit details -
Merge pull request #65 from cloudfoundry/bugfix/jammy-support
add jammy compability
Configuration menu - View commit details
-
Copy full SHA for 83597c9 - Browse repository at this point
Copy the full SHA 83597c9View commit details -
we should test this release and jammy and bionic stemcells as these are both currently in use with the OSS community. add additional acceptance job for jammy and update contraints on passing both jobs.
nouseforaname committedJul 20, 2022 Configuration menu - View commit details
-
Copy full SHA for 9144afc - Browse repository at this point
Copy the full SHA 9144afcView commit details
Commits on Sep 10, 2022
-
Configuration menu - View commit details
-
Copy full SHA for bd641bd - Browse repository at this point
Copy the full SHA bd641bdView commit details
Commits on Dec 3, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 323855b - Browse repository at this point
Copy the full SHA 323855bView commit details
Commits on Dec 10, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 6693ce7 - Browse repository at this point
Copy the full SHA 6693ce7View commit details
Commits on Jan 7, 2023
-
Configuration menu - View commit details
-
Copy full SHA for 2488bfb - Browse repository at this point
Copy the full SHA 2488bfbView commit details
Commits on Jan 10, 2023
-
Configuration menu - View commit details
-
Copy full SHA for 7c42338 - Browse repository at this point
Copy the full SHA 7c42338View commit details
Commits on Feb 11, 2023
-
Configuration menu - View commit details
-
Copy full SHA for f5985ca - Browse repository at this point
Copy the full SHA f5985caView commit details
Commits on Mar 11, 2023
-
Configuration menu - View commit details
-
Copy full SHA for aa5e47e - Browse repository at this point
Copy the full SHA aa5e47eView commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v22.1.2...v22.1.3