{"push_id":2381476342,"size":6,"distinct_size":6,"ref":"refs/heads/master","head":"a86bf4ec17992994b23b452666685786b6a07158","before":"6d583ffdc670c454fdd5970f0d6356e504c7ffac","commits":[{"sha":"63e123631b7484ef65656f87f8d693daa6a6e29c","author":{"name":"Micah Abbott","email":"7ad34b37f0d62ad63262ccf13140a91c2fdd558c@gmail.com"},"message":"papr: remove usage of Fedora 26 (#342)\n\nFedora 26 is dead to me.\r\n\r\nRemove the CI checks using a Fedora 26 host (which were always\r\nfailing on rebasing to a commit on the stable branch) and start using\r\nthe Fedora 27 Docker images.","distinct":true,"url":"https://api.github.com/repos/mike-nguyen/atomic-host-tests/commits/63e123631b7484ef65656f87f8d693daa6a6e29c"},{"sha":"2531a1bdd266a2cdb737a0c86d7785acfbe7ee05","author":{"name":"Micah Abbott","email":"7ad34b37f0d62ad63262ccf13140a91c2fdd558c@gmail.com"},"message":"k8s_set_facts: setup facts when kube node RPM not installed (#341)\n\nThe logic for determining the use of system containers was missing a\r\ncase when the `kubernetes-node` RPM was not installed on the host, but\r\nthe host was also not a Fedora/CentOS platform.  For example, our\r\ninternal 'autobrew' streams.\r\n\r\nThis updates the logic to handle this case.","distinct":true,"url":"https://api.github.com/repos/mike-nguyen/atomic-host-tests/commits/2531a1bdd266a2cdb737a0c86d7785acfbe7ee05"},{"sha":"8d1b083469383d18b48c0445b60a40f8f1fd2948","author":{"name":"Micah Abbott","email":"7ad34b37f0d62ad63262ccf13140a91c2fdd558c@gmail.com"},"message":"ci: enable extra args to be passed to .test_director (#343)\n\n* ci: enable extra args to be passed to .test_director\r\n\r\nThe `centos/7/atomic` context has been consistently failing because\r\nthere are AVC denials from the kernel that are present in the version\r\nof CentOS AH we are using.  This is preventing any useful CI checks\r\nfrom being run on that platform.\r\n\r\nThis change introduces a simple check to the `.test_director` script to\r\nsee if any arguments were passed to the script.  This way, we are able\r\nto skip tags we know are causing problems in our CI checks.\r\n\r\nIn order to utilize this change, I re-arranged the order of contexts\r\nin the `.papr.yml` file in order to maintain inheritence between the\r\ncontexts and only pass in the extra args to the `centos/7/atomic`\r\ncontext.\r\n\r\n* fixup! ci: enable extra args to be passed to .test_director","distinct":true,"url":"https://api.github.com/repos/mike-nguyen/atomic-host-tests/commits/8d1b083469383d18b48c0445b60a40f8f1fd2948"},{"sha":"c58510be2df8ae37a21efc0fbd8276f7a38213a9","author":{"name":"Micah Abbott","email":"7ad34b37f0d62ad63262ccf13140a91c2fdd558c@gmail.com"},"message":"roles: new role to validate firewalld install/config (#340)\n\n* roles: new role to validate firewalld install/config\r\n\r\nThis introduces a new role which can be used to validate the\r\ninstallation/configuration of the `firewalld` service.  It will\r\ndetermine if the host under test should have `firewalld` installed and\r\nhow it should be configured if it is installed.\r\n\r\nThis initial attempt is very simple, but could be expanded to do more\r\ncomplex checks if desired.\r\n\r\nThe role is used in the `improved-sanity-test` before the host is\r\nupgraded and after upgrade.\r\n\r\nCloses #315\r\n\r\n* fixup! roles: new role to validate firewalld install/config","distinct":true,"url":"https://api.github.com/repos/mike-nguyen/atomic-host-tests/commits/c58510be2df8ae37a21efc0fbd8276f7a38213a9"},{"sha":"e7bf96db30f9c643f8b63339601ba07b152b026c","author":{"name":"Micah Abbott","email":"7ad34b37f0d62ad63262ccf13140a91c2fdd558c@gmail.com"},"message":"use 'rpm_ostree_status' role for all the JSON output (#348)\n\nWe had a bunch of instances in the tree where we were doing\r\n`rpm-ostree status --json` and then going through the motions to parse\r\nthe JSON to determine things like the booted deployment, etc.\r\nAdditionally, we were littering our test logs with the 'noisy' keys\r\nfrom the JSON output that were handled in #301.\r\n\r\nThis change rips out all the invocations of `rpm-ostree status --json`\r\nand replaces them with the usage of the `rpm_ostree_status` role.  Now\r\nwe have a consistent way of dealing with the JSON output from the\r\n`status` command and only one place where we have to make changes if\r\nneeded.","distinct":true,"url":"https://api.github.com/repos/mike-nguyen/atomic-host-tests/commits/e7bf96db30f9c643f8b63339601ba07b152b026c"},{"sha":"a86bf4ec17992994b23b452666685786b6a07158","author":{"name":"Micah Abbott","email":"7ad34b37f0d62ad63262ccf13140a91c2fdd558c@gmail.com"},"message":"roles: adapt to Rawhide == F29 (#350)\n\nWe have to bump our $releasever for Rawhide now that F28 has branched,\r\nwhich means Rawhide == F29.\r\n\r\nI've added the necessary files to cover this change as well as\r\nrearranged some things under `selinux_verify/vars` to make a little\r\nmore sense (I hope).\r\n\r\nWhile I was mucking around in here, I continued to remove references\r\nto older versions of Fedora (24,25) where possible.","distinct":true,"url":"https://api.github.com/repos/mike-nguyen/atomic-host-tests/commits/a86bf4ec17992994b23b452666685786b6a07158"}]}
{"actor":{"display_login":"mike-nguyen"}}