• Login
    • Report A Bug
    • System Information
    • System Tests
    • System Policies
    • Code Documentation
    • Occam Source Code
    • Web Client Source Code
    • About Occam
    • Acknowledgements
    • Guides / Documentation
    • Publications

translation missing: en.flash.saving
translation missing: en.flash.error
  • Bibliography Data
  • Metadata
collection
    coreutils8.27
    QmPTRt7F2LqsvivzcgnNZZAmUVCQM7qnoTqMPJCKVxFH9x
    5dsJEkGiokXy6VSpQEuNsEgFUZs4pS
      QmPTRt7F2LqsvivzcgnNZZAmUVCQM7qnoTqMPJCKVxFH9x
      5dsJEkGiokXy6VSpQEuNsEgFUZs4pS

      • Details
      • Build
      • Files
      • History
        • JavaScript must be enabled.

          There was an error retrieving this content.

          The content could not be found.

        • Build

          Help

          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.

          • Run Queue
          • New
          • Manifest
          • Log
          • Run Queue
          • Run Queue

          Listing /usrHelp

          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.

            Cannot upload file: Read only access.

            ..
            application/octet-streambin
            ...
            • Download As Zip
            application/octet-streamshare
            ...
            • Download As Zip
            application/octet-streamlibexec
            ...
            • Download As Zip
            Drag Here
            • Building

              collectioncoreutils

              Providing
              linuxx86-64

              singularity-environmentLinux

              Backend

              singularity

              Dispatch To

              Occam Server
              • local

                My Computer

              • default

                Occam Server

            • ID

              QmUqxLpe7XZeznFUVs7YDN2nUkQ8wC2NwrZ3J67nTJNW9V

              Hash

              ba5a6093976c2bd3a70db05bcecba4499b9a06538e5b0fcb746624563bce7a07

              Time

              1 min 8 secs

              Date

              Wed, 28 Jul 2021 23:40:09 +0000

              Backend

              singularity

              1. task

                Task to build coreutils on singularity

                1. singularity-environment

                  Linux

                  1. compiler

                    g++4.7.4

                  2. runtime

                    glibc2.25-bootstrap

                  3. runtime

                    g++4.7.4

                  4. library

                    stdc++4.7.4

                  5. library

                    gmp6.1.2

                  6. library

                    mpfr3.1.5

                  7. library

                    mpc1.0.3

                  8. library

                    cloog0.18.5-bootstrap.s2

                  9. library

                    isl0.13-bootstrap.s2

                  10. library

                    osl0.9.2-bootstrap.s2

                  11. library

                    ppl1.2-bootstrap.s2

                  12. collection

                    build1.0

                  13. headers

                    linux4.9.33-bootstrap.s2

                  14. application

                    gzip1.8-bootstrap.s2

                  15. collection

                    texinfo4.9-bootstrap.s2

                  16. language

                    perl5.26.2-bootstrap.s2

                  17. library

                    ncurses6.0-bootstrap.s2

                  18. library

                    readline7.0-bootstrap.s2

                  19. application

                    db5.3.28

                  20. application

                    gdbm1.13-bootstrap.s2

                  21. perl-module

                    Encode2.89-bootstrap.s2

                  22. application

                    tar1.29-bootstrap.s2

                  23. collection

                    diffutils3.5

                  24. application

                    file5.31

                  25. library

                    zlib1.2.11

                  26. language

                    bash4.4-bootstrap.s2

                  27. collection

                    coreutils8.27-bootstrap.s2

                  28. application

                    make4.2.1-bootstrap.s2

                  29. application

                    sed4.4-bootstrap.s2

                  30. collection

                    binutils2.28-bootstrap.s2

                  31. application

                    flex2.6.4

                  32. application

                    m41.4.18

                  33. application

                    grep3.0-bootstrap.s2

                  34. application

                    gawk4.1.4

                  35. collection

                    shadow4.5-bootstrap.s2

                  36. collection

                    findutils4.6.0

                  37. application

                    which2.21-bootstrap.s2

                  38. application

                    pkg-config0.29.2-bootstrap

                  39. collection

                    coreutils

                    The basic file, shell and text manipulation utilities of the GNU operating system.

            Run Queue List

            • Queue
            • July 28, 2021 23:40
          • 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
          Do you wish to proceed?

          Confirm message?