error-message
success-message
saving-message
warning-message
JavaScript must be enabled.
There was an error retrieving this content.
The content could not be found.
JavaScript must be enabled.
There was an error retrieving this content.
The content could not be found.
This panel views the builds of the artifact.
Many objects can elect to have a "build" phase. This is a transforative action that takes the content of the object and produces a useful result that is considered the actual representation of the object.
For software, this is the actual build or compilation step. Source code is the data comprising the object in the archive. The build step turns the text source code into a machine usable binary that would actually be used to invoke the software. That build step can be described in the object and then deployed to produce such a binary. The log and resulting files can be explored here.
Any completed build of an object will show up here. Such a build was a deployment of the object in some form. That is, much like running an object, it had to have a proper environment created for it consisting of the object (source code, etc) and dependencies (the compiler it needs, etc). Builds might use historic components also themselves archived in the system. To ensure these are more properly repeatable, each build records exactly the software and data used in that environment.
When you select a build, it will present you with a description of that environment in what is called a task. The manifest itself is the metadata for the task which lists the dependencies. Interacting with that list allows you to view the dependencies from the point of view of the version used in the build.
Other metadata is listed as well. The identifier for the build is simply the identifier of the task (which is itself an object in the archive.) The hash of all the resulting files and logs to uniquely and verifiably identify the build anywhere. The time elapsed to produce the build at the time it was built, which is itself listed as the date.
You can see all historic builds in the queue side-panel. Each will be listed by their date of deployment.
You can invoke a new build by going to the "New" tab or by selecting "Queue" in the queue side-panel. This gives you a listing very similar to that in the "Run" panel, which lists the possible environment needed to perform the build and allow you to override which artifacts and software are used to do so.
This is the file listing that shows the files within directories of this current object.
When you are editing your own objects, you can perform some actions to update the files. We will discuss these actions now.
You can upload files by either dragging them into the file listing from your local machine or by using the buttons near the listing.
You can create a new file by using one of the buttons near the listing. This will allow you to give the file a name which you can then click on to open the blank file to edit it further.
You can add a new directory to organize your files by using another button near the listing. Once you press the button, you can name the directory and then click on it to traverse to this empty directory.
Note that you cannot have a directory or file with the same name in the same directory. This includes not being able to have a directory and file with the same name.
Clicking on a file in the listing will open the file. If you are editing the object, then it may open an editor for that file. Otherwise you will receive a read-only view of the file. The viewer or editor will depend on your associations for the type of file. Most text files, for instance, will open in a text editor.
The actions button to the right of each file in the listing will select further actions to be done on each file. These actions will be discussed now.
The remove action will delete the file from the current view of the object when you have such permissions.
The download action will download a copy of the file to your local machine.
The set as main action will set the given file as the main file for
the object. For many objects, this has special significance. It will
essentially set the file
field of the object to the path to this file.
You can refer to it in a run or build command to make the object more
flexible and extensible instead of hard-coding such paths. Other
objects might expect a file
to be chosen when they take an object as
input in a workflow. In these cases, the main file highlights which
file is most important. Occam especially handles HTML documents and
widgets by loading the main file as the entry point to the interactive
program or document.
Qmf1DAv1MPHLzHAm6z8J3eutbuGRuCBu8BrX9axe3MdwFs
db805b40e098ac588770204f7ba7affee42ff22ef964f73130219ce725acb1a7
17 secs
Thu, 19 Aug 2021 05:39:21 +0000
singularity
Task to build c-ares on singularity
Linux
build1.0
linux4.20.9
glibc2.26
g++10.3.0
stdc++10.3.0
gmp6.1.2
mpfr3.1.5
mpc1.0.3
gzip1.8
texinfo4.9
perl5.26.2
ncurses6.0
readline7.0
db5.3.28
gdbm1.13
Encode2.89
tar1.29
diffutils3.5
file5.31
zlib1.2.11
bash4.4
coreutils8.27
make4.2.1
sed4.4
binutils2.36.1
elf0.185
bzip21.0.6
xz5.2.3
zstd1.5.0
lz41.8.0
archive3.5.1
acl2.2.52
attr2.4.47
expat1.6.2
openssl1.1.1.k
microhttpd0.9.73
gnutls3.7.2
idn22.3.1
unistring0.9.10
tasn14.12
nettle3.7.3
p11-kit0.23.9
ffi3.4.2
curl7.56.0
nghttp21.23.1
psl0.18.0
mnl1.0.4
icu59.1
ssh21.8.0
ca-certificates20170307
ca-certificates-mozilla3.33
sqlite3.20.1
nspr4.17
ca-certificates-cacert20140824
ca-certificates-utils20170307
flex2.6.4
m41.4.18
grep3.6
pcre8.41
gawk4.1.4
shadow4.5
findutils4.6.0
which2.21
pkg-config0.29.2
g++10.3.0
cmake3.20.5
hicolor-icon-theme0.17
uv1.41.0
nsl1.2.0
tirpc1.1.4
rhash1.4.1
jsoncpp1.8.1
c-ares
A C library for asynchronous DNS requests.
JavaScript must be enabled.
There was an error retrieving this content.
The content could not be found.
JavaScript must be enabled.
There was an error retrieving this content.
The content could not be found.
Generating tasks and queuing jobs...
JavaScript must be enabled.
There was an error retrieving this content.
The content could not be found.
JavaScript must be enabled.
There was an error retrieving this content.
The content could not be found.
Confirm message?