summaryrefslogtreecommitdiff
path: root/Makefile
Commit message (Collapse)AuthorAge
* Update registrar unit tests to match them of cri-oSascha Grunert2019-04-04
| | | | | | | - Add the test framework abstraction - Update the unit tests to run with ginkgo Signed-off-by: Sascha Grunert <sgrunert@suse.com>
* Bump gitvalidation epochMatthew Heon2019-03-30
| | | | Signed-off-by: Matthew Heon <matthew.heon@pm.me>
* zsh completionEd Santiago2019-03-13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Weekend hack by someone who doesn't grok zsh completion but who finds it deeply offensive that most completion files have an unmaintainable duplication of options and arguments. The idea behind this one is to discover the command line using --help, with a few hardcoded helpers for discovering containers, images, pods, and figuring out which args take files/dirs as args. Working remarkably well. I am using this in my daily routine and wondering how I ever managed without it. It's not perfect -- a future version can perhaps show only stopped containers for podman rm, only running ones for podman stop -- but ROI seems low on that given my limited zsh completion skills. Sadly, I can't figure out how to write a regression test suite for this. It would be lovely to have a list if partial command lines and expected completions, because the history of this change is that (seemingly) minor tweaks in one place cause breakage in another. Does anyone know of such a framework? Still... working well enough to ship, IMO. Signed-off-by: Ed Santiago <santiago@redhat.com>
* Add gating tasksbaude2019-03-13
| | | | | | | | | | | to protect against regressions, we need to add a few gating tasks: * build with varlink * build podman-remote * build podman-remote-darwin we already have a gating task for building without varlink Signed-off-by: baude <bbaude@redhat.com>
* Merge pull request #2598 from mheon/crio_umount_is_uselessOpenShift Merge Robot2019-03-09
|\ | | | | We don't use crio-umount.conf
| * We don't use crio-umount.confMatthew Heon2019-03-08
| | | | | | | | | | | | | | | | | | | | | | It also causes conflicts with CRI-O packages. Also, change the path on seccomp.json so it lives in /usr/share by default, with everything else. Fixes #2596 Signed-off-by: Matthew Heon <mheon@redhat.com>
* | ginkgo status improvementsbaude2019-03-08
|/ | | | | | | a series of improvements to our ginkgo test framework so we can get better ideas of whats going on when run in CI Signed-off-by: baude <bbaude@redhat.com>
* Merge pull request #2528 from cevich/more_timeOpenShift Merge Robot2019-03-05
|\ | | | | Globally increase test timeout to 90-minutes
| * Globally increase test timeout to 90-minutesChris Evich2019-03-04
| | | | | | | | Signed-off-by: Chris Evich <cevich@redhat.com>
* | Bump gitvalidation epochMatthew Heon2019-03-04
|/ | | | Signed-off-by: Matthew Heon <matthew.heon@pm.me>
* Bump gitvalidation epochMatthew Heon2019-03-01
| | | | Signed-off-by: Matthew Heon <matthew.heon@pm.me>
* Bump gitvalidation epochMatthew Heon2019-02-26
| | | | Signed-off-by: Matthew Heon <matthew.heon@pm.me>
* build varlink without GOPATHbaude2019-02-13
| | | | | | | | | | when gopath was not explicitly set, make would fail due to the varlink generator. this symlink in the makefile addresses that. fixes: #1842 Signed-off-by: baude <bbaude@redhat.com>
* Makefile: Don't include quotes around GIT_COMMITLars Karlitski2019-02-12
| | | | | | These quotes were included in the varlink `GetVersion()` call. Signed-off-by: Lars Karlitski <lars@karlitski.net>
* Remove urfave/cli from libpodbaude2019-02-11
| | | | | | | This is the final cleanup to remove urfave/sli from libpod. Removed old, disabled tests that have not been run in over a year. Signed-off-by: baude <bbaude@redhat.com>
* Migrate to cobra CLIbaude2019-02-08
| | | | | | | | We intend to migrate to the cobra cli from urfave/cli because the project is more well maintained. There are also some technical reasons as well which extend into our remote client work. Signed-off-by: baude <bbaude@redhat.com>
* Merge pull request #2288 from vrothberg/vendor-docsOpenShift Merge Robot2019-02-07
|\ | | | | Vendor docs
| * make vendor: always check for latest vndrValentin Rothberg2019-02-07
| | | | | | | | | | | | | | | | | | | | | | | | @baude and I have recently debugged a `make vendor` issue, where different versions of `vndr` leave slightly different states behind. This ultimately leads to inconsistencies with the CI, which always fetches the latest version. To avoid such issues in the future, always use the latest version of `vndr` by checking for new versions of it prior to execution. Signed-off-by: Valentin Rothberg <rothberg@redhat.com>
* | Add varlink generate to the make documentationHervé Beraud2019-02-07
|/ | | | | | | Minor improvement who add helping comment to the varlink generate target. Signed-off-by: Hervé Beraud <hberaud@redhat.com>
* Merge pull request #2283 from 4383/improve-makefileOpenShift Merge Robot2019-02-06
|\ | | | | Generate make helping message dynamicaly.
| * Generate make helping message dynamicaly.Hervé Beraud2019-02-06
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Generate make helping message dynamicaly by using python code snippet inside Makefile. All commented make targets will be added to the help message. To be added to the helping message comment need to start with '## '. These specials comments are detected by the python code. Python code generate the helping output from these results. Notice that this commit introduce a dependency with python (compatible python 2 and 3). Signed-off-by: Hervé Beraud <hberaud@redhat.com>
* | Makefile: minor fix to reenable system testsEd Santiago2019-02-06
|/ | | | | | | | | | PR #2259 removed the .install.gomega Makefile target but didn't clean up two references to it. Do so now. Also, when setting up GOPKGBASEDIR symlink, use -f (force) flag; otherwise subsequent makes will fail. Signed-off-by: Ed Santiago <santiago@redhat.com>
* Merge pull request #2270 from cevich/fail_fasterOpenShift Merge Robot2019-02-06
|\ | | | | Apply 45min timeout to integration tests
| * Apply 50min timeout to integration testsChris Evich2019-02-05
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | IMHO, longer than this waiting for automated testing is "too long". Scientificaly speaking, based on thousands of runs across many platforms, successful runs always happen in less time. Normally Ubuntu passes in 35-40 minutes, and the Fedoras do it in 25-30. If they take longer, something is likely badly broken. In that case, it's better to fail within a short/defined time, than wait for the (much longer) automation-level timeout and inevitable failure. Signed-off-by: Chris Evich <cevich@redhat.com>
* | Cirrus: add vendor_check_taskValentin Rothberg2019-02-06
| | | | | | | | | | | | | | | | | | | | | | * Make sure that all vendored dependencies are in sync with the code and the vendor.conf by running `make vendor` with a follow-up status check of the git tree. * Vendor ginkgo and gomega to include the test dependencies. Signed-off-by: Chris Evic <cevich@redhat.com> Signed-off-by: Valentin Rothberg <rothberg@redhat.com>
* | tests: allow to override the OCI runtimeGiuseppe Scrivano2019-02-05
|/ | | | Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
* Merge pull request #2253 from kunalkushwaha/quick-dockerfile-buildOpenShift Merge Robot2019-02-04
|\ | | | | Reduce Dockerfile based build time for libpod.
| * Reduce Dockerfile based build time for libpod.Kunal Kushwaha2019-02-01
| | | | | | | | | | | | | | libpod code added at end of Dockerfile, avoids git clone of other packages in Dockerfile on subsequent builds. Signed-off-by: Kunal Kushwaha <kushwaha_kunal_v7@lab.ntt.co.jp>
* | Set SELinux type on bin/podman after installChris Evich2019-01-30
|/ | | | | | | | | | | Different components of testing reference the podman binary differently. While they are identical in content, their SELinux types are not the same, depending on build location. Avoid confusion and test failures by always matching the bin/podman SELinux type to that of $BINDIR/podman **after** install. This ensures even if the code or default contexts change, a subsequent `make install` will re-match the SELinux type. Signed-off-by: Chris Evich <cevich@redhat.com>
* Update README for v1.0.0Matthew Heon2019-01-16
| | | | | | | Also bump gitvalidation epoch - we usually do this every release, but v1.0.0 is on a branch so we need a separate commit for master Signed-off-by: Matthew Heon <matthew.heon@pm.me>
* Run integrations test with remote-clientbaude2019-01-14
| | | | | | | | | | | | Add the ability to run the integration (ginkgo) suite using the remote client. Only the images_test.go file is run right now; all the rest are isolated with a // +build !remotelinux. As more content is developed for the remote client, we can unblock the files and just block single tests as needed. Signed-off-by: baude <bbaude@redhat.com>
* Add darwin support for remote-clientbaude2019-01-11
| | | | | | | | Add the ability to cross-compile podman remote for OSX. Also, add image exists and tag to remote-client. Signed-off-by: baude <bbaude@redhat.com>
* vendor make targetValentin Rothberg2019-01-11
| | | | | | | Add a `make vendor` target calls `vndr` with a specified whitelist to avoid deleting important files (currently the varlink/go project). Signed-off-by: Valentin Rothberg <rothberg@redhat.com>
* Remove easyjson in preparation for switch to jsoniterMatthew Heon2019-01-10
| | | | | | | | | The jsoniter library does not require code generation, which is a massive advantage over easyjson (it's also about the same in performance). Begin moving over to it by removing the existing easyjson code. Signed-off-by: Matthew Heon <matthew.heon@pm.me>
* Move python code from contrib to it's own repo python-podmanJhon Honce2019-01-10
| | | | Signed-off-by: Jhon Honce <jhonce@redhat.com>
* Add Validate completionsDaniel J Walsh2019-01-08
| | | | | | | | In podman 0.12.0 we have invalid completions. These should have been caught during testing. This check will throw an error if the completions do not successfully execute. Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
* Merge pull request #2098 from baude/remoteOpenShift Merge Robot2019-01-07
|\ | | | | Add ability to build golang remote client
| * Add ability to build golang remote clientbaude2019-01-07
| | | | | | | | | | | | | | | | | | | | | | Add the ability to build a remote client in golang that uses all the same front-end cli code and output code. The initial limitations here are that it can only be a local client while the bridge and resolver code is being written for the golang varlink client. Tests and docs will be added in subsequent PRs. Signed-off-by: baude <bbaude@redhat.com>
* | Readd Python testingMatthew Heon2019-01-04
| | | | | | | | | | | | | | We accidentally merged a PR with a commit temporarily disabling the Python tests. Reenable them here. Signed-off-by: Matthew Heon <matthew.heon@pm.me>
* | DO NOT MERGE temporarily remove python testsMatthew Heon2019-01-04
| | | | | | | | | | | | | | | | | | It's impossible to get good debug out of the python tests, so nuke them for now so I can figure out what's wrong. DO NOT MERGE THIS COMMIT Signed-off-by: Matthew Heon <matthew.heon@pm.me>
* | add container-init supportValentin Rothberg2019-01-04
|/ | | | | | | | | | | | | | | | | | | Add support for executing an init binary as PID 1 in a container to forward signals and reap processes. When the `--init` flag is set for podman-create or podman-run, the init binary is bind-mounted to `/dev/init` in the container and "/dev/init --" is prepended to the container's command. The default base path of the container-init binary is `/usr/libexec/podman` while the default binary is catatonit [1]. This default can be changed permanently via the `init_path` field in the `libpod.conf` configuration file (which is recommended for packaging) or temporarily via the `--init-path` flag of podman-create and podman-run. [1] https://github.com/openSUSE/catatonit Fixes: #1670 Signed-off-by: Valentin Rothberg <rothberg@redhat.com>
* Merge pull request #1757 from kunalkushwaha/contrib-perftestOpenShift Merge Robot2018-12-20
|\ | | | | perf test a stress test to profile CPU load of podman
| * perf test a stress test to profile CPU load of podmanKunal Kushwaha2018-12-19
| | | | | | | | Signed-off-by: Kunal Kushwaha <kushwaha_kunal_v7@lab.ntt.co.jp>
* | Makefile: validate that each commit can at least buildGiuseppe Scrivano2018-12-19
|/ | | | | | | | | it is very useful when using git bisect that at least the commit can build. got inspiration from: https://twitter.com/pid_eins/status/1072797993760423941 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
* Bump gitvalidation epochMatthew Heon2018-12-13
| | | | Signed-off-by: Matthew Heon <matthew.heon@gmail.com>
* Makefile tweaks to fix make shellMatthew Heon2018-12-12
| | | | | | | | | Also, bump the Dockerfile to use the latest Golang image, as most of our testing is now done on 1.11 Fixes: #1999 Signed-off-by: Matthew Heon <matthew.heon@gmail.com>
* No need to use `-i` in go build (with go 1.10 and above)Vincent Demeester2018-12-11
| | | | | | | | | | | | | | | > The go build command now maintains a cache of recently built packages, separate from the installed packages in $GOROOT/pkg or $GOPATH/pkg. The effect of the cache should be to speed builds that do not explicitly install packages or when switching between different copies of source code (for example, when changing back and forth between different branches in a version control system). The old advice to add the -i flag for speed, as in go build -i or go test -i, is no longer necessary: builds run just as fast without -i. This should also fix podman builds for NixOS, snap-installed go, … Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
* Bump gitvalidation epochMatthew Heon2018-12-07
| | | | Signed-off-by: Matthew Heon <matthew.heon@gmail.com>
* Merge pull request #1788 from cevich/cirrus_base_imagesOpenShift Merge Robot2018-12-07
|\ | | | | Codify and document base-image production + Enable testing with Fedora
| * Cirrus: Use Makefile for image-buildingChris Evich2018-12-06
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The packer tool takes JSON as input for the details of producing VM images to be used for PR CI-testing. JSON is not a very human-friendly format, without support for comments and frequently containing lots of duplicate data. Fix this by using a Makefile + simple python one-liner to convert from a human-friendly YAML format into packer-native JSON. This allows use of anchors/aliases to reduce duplication, and allows inline comments for easier maintainability. This also allows separating the 'test' action from the 'build' action, for earlier and better syntax problem detection. Lastly, there are some minor ``lib.sh`` and ``integration_test.sh`` updates to support future work, and slightly improve the build and test environments. Signed-off-by: Chris Evich <cevich@redhat.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-12-26 22:05:17 +0000