| /openbmc/openbmc/poky/bitbake/lib/toaster/tests/browser/ |
| H A D | test_builddashboard_page_artifacts.py | 21 """ Tests for artifacts on the build dashboard /build/X """
41 Check whether the "Build artifacts" heading is visible (True if it
44 return self.element_exists('[data-heading="build-artifacts"]')
55 If a build produced no artifacts, the artifacts heading and images
67 # check build artifacts heading
68 msg = 'Build artifacts heading should not be displayed for non-image' \
78 If a build produced SDK artifacts, they should be shown, but the section
101 # check build artifacts heading
102 msg = 'Build artifacts heading should be displayed for SDK ' \
103 'builds which generate artifacts'
[all …]
|
| /openbmc/openbmc/poky/meta/lib/oeqa/utils/ |
| H A D | postactions.py | 43 # Artifacts retrieval
64 bb.warn("Could not load artifacts list, skip artifacts retrieval")
71 raise Exception("Error while fetching compressed artifacts")
76 bb.warn(f"Can not retrieve artifacts from test target: {e}")
84 artifacts = d.getVar("TESTIMAGE_FAILED_QA_ARTIFACTS")
85 …# Allow all the code to be disabled by having no artifacts set, e.g. for systems with no ssh suppo…
86 if not artifacts:
102 action(d, tc, artifacts, outputdir)
|
| /openbmc/qemu/.gitlab-ci.d/ |
| H A D | buildtest.yml | 20 artifacts: true
29 artifacts: true
50 artifacts: true
59 artifacts: true
81 artifacts: true
90 artifacts: true
99 artifacts: true
138 artifacts: true
147 artifacts: true
156 artifacts: true
[all …]
|
| H A D | buildtest-template.yml | 48 # rebuilding all the object files we skip in the artifacts
50 artifacts:
80 # doctests need all the compilation artifacts
86 artifacts:
102 artifacts:
|
| H A D | static_checks.yml | 67 artifacts: true
68 artifacts:
|
| H A D | opensbi.yml | 69 artifacts:
71 paths: # 'artifacts.zip' will contains the following files:
|
| H A D | custom-runners.yml | 21 artifacts:
|
| /openbmc/qemu/rust/ |
| H A D | .gitignore | 1 # Ignore any cargo development build artifacts; for qemu-wide builds, all build
2 # artifacts will go to the meson build directory.
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | wic.rst | 16 OpenEmbedded build artifacts. Image generation is driven by partitioning
22 section. When you apply the command to a given set of build artifacts, the
56 of OpenEmbedded build artifacts instead of package installation and
58 artifacts.
85 - You need to have the build artifacts already available, which
89 using Wic, the current version of Wic requires the artifacts in the
171 you need for specifying the OpenEmbedded build artifacts that are used
174 - *Raw Mode:* You explicitly specify build artifacts through Wic
180 artifacts. You just supply a kickstart file and the name of the image
181 from which to use artifacts.
[all …]
|
| /openbmc/openbmc/poky/bitbake/lib/toaster/toastergui/templates/ |
| H A D | builddashboard.html | 80 <h2 data-heading="build-artifacts">Build artifacts</h2>
83 …<div class="well well-transparent dashboard-section" data-artifacts-for-target="{{target.target.pk…
129 <ul class="list-unstyled" data-links="image-artifacts">
141 Kernel artifacts
144 <ul class="list-unstyled" data-links="kernel-artifacts">
158 SDK artifacts
161 <ul class="list-unstyled" data-links="sdk-artifacts">
181 <!-- other artifacts -->
183 <h2>Other artifacts</h2>
188 …<span class="glyphicon glyphicon-question-sign get-help" title="Build artifacts discovered in <i>t…
[all …]
|
| /openbmc/openbmc/poky/meta/recipes-core/images/ |
| H A D | core-image-tiny-initramfs.bb | 6 actually generate an image but rather generates boot and rootfs artifacts \
24 # don't actually generate an image, just the artifacts needed for one
|
| /openbmc/openbmc/poky/scripts/lib/wic/ |
| H A D | help.py | 150 various build artifacts required to build the image.
154 the corresponding artifacts are typically found in a normal
163 artifacts from e.g. core-image-sato.
169 the boot artifacts (e.g. /EFI or /syslinux dirs) to use as the
193 When 'wic -e' is used, the locations for the build artifacts
619 OpenEmbedded build artifacts. Image generation is driven by
624 artifacts, the result is an image or set of images that can be
650 artifacts that will be used in creating the image: 'raw' and
653 If used in 'raw' mode, artifacts are explicitly specified via
658 artifacts used to create the image.
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/emacs/files/ |
| H A D | avoid-running-host-binaries-for-sanity.patch | 3 Emacs introduced a sanity-check for the build artifacts, where it
34 +# Avoid calling target binaries from the host and simply assume our build artifacts work.
|
| /openbmc/openbmc/meta-arm/ |
| H A D | .gitlab-ci.yml | 77 artifacts:
118 artifacts:
199 artifacts:
241 artifacts:
256 artifacts:
|
| /openbmc/qemu/tests/functional/ |
| H A D | test_aarch64_sbsaref.py | 58 ('https://artifacts.codelinaro.org/artifactory/linaro-419-sbsa-ref/'
63 ('https://artifacts.codelinaro.org/artifactory/linaro-419-sbsa-ref/'
|
| /openbmc/openbmc/poky/bitbake/lib/toaster/tests/builds/ |
| H A D | README | 13 - TOASTER_DIR (where toaster keeps it's artifacts)
|
| /openbmc/openbmc/poky/scripts/ |
| H A D | wic | 123 raise WicError("The following build artifacts are not specified: %s" %
208 logger.info("Build artifacts not found, exiting.")
209 logger.info(" (Please check that the build artifacts for the machine")
211 logger.info(" are the correct artifacts for the image (.wks file)).\n")
321 help="name of the image to use the artifacts from "
327 help="path to the dir containing the boot artifacts "
|
| /openbmc/openbmc/poky/scripts/esdk-tools/ |
| H A D | wic | 123 raise WicError("The following build artifacts are not specified: %s" %
208 logger.info("Build artifacts not found, exiting.")
209 logger.info(" (Please check that the build artifacts for the machine")
211 logger.info(" are the correct artifacts for the image (.wks file)).\n")
321 help="name of the image to use the artifacts from "
327 help="path to the dir containing the boot artifacts "
|
| /openbmc/u-boot/board/phytec/pfla02/ |
| H A D | README | 18 This generates the artifacts SPL and u-boot.img.
|
| /openbmc/openbmc/poky/meta/recipes-core/picolibc/ |
| H A D | picolibc.inc | 7 # are GPLv2 and GeneratePicolibcCrossFile.sh is AGPL3 but not part of the artifacts.
|
| /openbmc/openbmc/meta-arm/ci/ |
| H A D | download-lockfile.py | 27 artefact = project.artifacts.download(ref_name=args.refspec, job="update-repos")
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/python3-django/ |
| H A D | 0001-Fixed-35980-Updated-setuptools-to-normalize-package.patch | 5 in built artifacts.
|
| /openbmc/openbmc/poky/meta/classes/ |
| H A D | toaster.bbclass | 340 # get list of artifacts from sstate manifest
359 artifacts = [fname.strip() for fname in fmanifest]
360 data = {"task": e.taskid, "artifacts": artifacts}
|
| /openbmc/openbmc/poky/bitbake/lib/bb/ui/ |
| H A D | buildinfohelper.py | 706 Save SDK artifacts to the database, associating them with a
1563 # request archival of the project artifacts
1673 task_artifacts = task_vars['artifacts']
1728 Scan for built image artifacts in DEPLOY_DIR_IMAGE and associate them
1746 # any image artifacts, so we can return immediately
1864 # copy image files and build artifacts from the
1874 logger.info('image artifacts for target %s cloned from ' \
1881 Return targets which could generate SDK artifacts, i.e.
1903 # targets which might have created SDK artifacts
1906 # location of SDK artifacts
[all …]
|
| /openbmc/openbmc/poky/meta/classes-recipe/ |
| H A D | kernel-artifact-names.bbclass | 10 # artifacts, but aren't kernel recipes themselves
|