Geeting error at Build Stage CI/CD

I am getting error on build stage while running pipeline.


CICD Error details.txt (791 Bytes)

@chandresh_agarwal

Can you show the build activity properties…

Also does your user have publish permissions?

Cheers

HI Anil,

Where can i check publish permissions?

I can publish process through my studio

@chandresh_agarwal

Are you using same user here as well which you used in studio?

Cheers

Yes same user I am using

@chandresh_agarwal

Mostly it might be that the package with same version already might be existing…to verify try deleting the package tenant → packages and then check

Cheers

Tried deleting the older package and pusing new code to GIT…that too didn’t worked

Hi @chandresh_agarwal ,

I have a couple of questions:

  1. Are you using the built-in pipelines or have defining your own?
  2. In case you are using the built-in one, would you please try to use the newer version from here: Update Process from Code Pipeline - RPA Component | UiPath Marketplace | Overview . This new version is using the 2.0.0 version of the UiPath.Pipelines.Activity package. More details here: Activities - Project compatibility

Thank you,
Alex

It is failing at clone stage now after upgrading the package

Would you please post the logs? Or if they are sensitive, you can share them with me privately.

Update.process.from.code execution started
ProjectPath: GIT Test/project.json
Committer username: Chandresh161
CommitSha: 12c0ddb38126b535637857cc28eac81ef35f07d2
RepositoryUrl: https://github.com/Chandresh161/GIT-Test.git
Build number: 4
[Clone project]: /tmp/1730119207997.003
"Cloned " + https://github.com/Chandresh161/GIT-Test.git + " To " + /tmp/1730119207997.003
Build: No space left on device
Update.process.from.code execution ended

Hello, in my company we’re considering to acquiring Robot Units to run pipelines as we find it very useful. But we’re encountering an issue when running Build.and.publish package, which resembles the error discussed in this thread.
These are our logs:

Process (string): Build.and.publish
Package (string): Build.and.publish
Package version (string): 1.0.17
State: Faulted
Start time: 11/05/2024, 11:16 AM
End time: 11/05/2024, 11:17 AM
Machine template: Pipelines serverless machine
Robot: pipelines robot-unattended
Account: pipelines robot
Host name: 39C2F65F-501B-0A00-F602-0B477A5618C9
Raw message (string): No space left on device System.Exception: No space left on device at System.Activities.Statements.Throw.Execute(CodeActivityContext context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
Build Number (string): 2
CommitSha (string): <redacted>
Committer user name (string): <redacted>
OrchestratorFolder: <redacted>
Orchestrator URL (string): <redacted>
ProjectPath (string): project.json
Repository branch (string): main
Repository type (string): git
Repository URL (string): <redacted>


-----------------------------------------------------------------------------------------------------------------------------------------------

-----------------------------------------------------------------------------------------------------------------------------------------------


1.Build.and.publish execution started
2.ProjectPath: project.json
3.CommitSha: <redacted>
4.RepositoryUrl: <redacted>
5.Committer username: <redacted>
6.Build number: 2
7.[Clone project]: /tmp/1730801786399.8584
8."Cloned " + <redacted> + " To " + /tmp/1730801786399.8584
9.Build: No space left on device
10.Build.and.publish execution ended

Afterward, we tried with another github repository and this time we got a more detailed exception message:

No space left on device : '/tmp/home/.nuget/packages/uipath/24.10.94.62718/bessvdqq.jiq'

The used machine is the Serverless machine (we’re using service trial robot units) created by default when setting up pipeline’s runtime:

imagen

Thank you